OpenEye Apex Network Video Recorder (NVR) firmware 3.2.9.376 uses an administrator password-reset...
Summary
Vulnerability reported (CVE-2026-92930). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
OpenEye Apex Network Video Recorder (NVR) firmware 3.2.9.376 uses an administrator password-reset unlock-code design that lacks a per-device secret or other server-side cryptographic material. An attacker with physical-console access and access to the privileged password-reset workflow can forge a valid unlock code offline and use it to reset the administrator password. The underlying design has been present since at least firmware 2.2.3.4.
Upgrade to version 3.5.4.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-92930 has been found.
Successful exploitation can lead to full system takeover. CVSS score: 6.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-92930" on the vendor's site.
CVE-2026-92930 — CWE-330 / CVSS v3 6.2
Attack vector: physical / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-330) has been reported.
Check the vendor advisory for the affected versions.
Severity: Medium (CVSS 6.2/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web portal.openeye.net
- web contact@securifera.com
- web nvd.nist.gov
- web securifera.com
- web github.com