CVE-2026-92929: Medium severity OpenEye Apex Network Video Recorder (NVR) vulnerability

Published Sep 22, 2026
·
Updated

OpenEye Apex Network Video Recorder (NVR) firmware 3.2.9.376 trusts an X-Forwarded-For header supplied by an arbitrary client when determining the request source address. An unauthenticated remote attacker can spoof a loopback address to bypass local-connection-only security controls exposed on the affected non-TLS web interfaces and disclose configuration information. The underlying design has been present since at least firmware 2.2.3.4.

Upgrade to version 3.5.4.

Affected Software

1 affected component
OpenEye Apex Network Video Recorder (NVR)>=2.2.3.4<3.5.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenEye Apex Network Video Recorder (NVR) firmware to a version that resolves this vulnerability.

    Fixed in 3.5.4

Event History

Sep 22, 2026
CVE Published
via MITRE·11:10 PM
Data Sourced
via MITRE·11:10 PM
RemedyDescriptionSeverityWeakness
Sep 23, 2026
Data Sourced
via NVD·12:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

OpenEye Apex NVR systems using the affected non-TLS web interfaces are exposed if they run firmware 3.2.9.376 or a version with the underlying design, which has been present since at least 2.2.3.4. The issue affects controls that rely on the request appearing to originate from a local connection.

2

What does an attacker need to exploit it?

An attacker needs remote network access to an affected non-TLS web interface. No authentication or user interaction is required; the attacker supplies a spoofed X-Forwarded-For header containing a loopback address.

3

What can successful exploitation allow?

Successful exploitation bypasses local-connection-only security controls and can disclose configuration information. The provided severity vector indicates confidentiality impact only, with no stated integrity or availability impact.

4

What should be done if the NVR cannot be upgraded immediately?

Restrict remote access to the affected non-TLS web interfaces so untrusted clients cannot reach them. This reduces the opportunity for an unauthenticated remote client to submit spoofed X-Forwarded-For headers; upgrade to firmware 3.5.4 when possible.

5

How can I determine whether a system may be affected?

Check the NVR firmware version and whether its non-TLS web interface is reachable by remote clients. Firmware 3.2.9.376 is affected, and the vulnerable design has existed since at least firmware 2.2.3.4; version 3.5.4 is the stated upgrade target.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203