Skip to main content
Vulnerability Database/CVE-2026-100291

CVE-2026-100291: Anjvision YSSD-RTMP-H5 Auth Bypass Flaw

CVE-2026-100291 is an authentication bypass vulnerability in Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4 affecting ONVIF service endpoints. This article covers the technical details, security impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100291 Overview

CVE-2026-100291 is a missing authentication vulnerability in Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4. Several Open Network Video Interface Forum (ONVIF) service endpoints process management requests without enforcing required authentication. An unauthenticated network attacker can invoke sensitive device operations directly. The weakness is classified under CWE-1188: Initialization of a Resource with an Insecure Default family of authentication failures, and is tracked in CISA ICS Advisory ICSA-26-272-05.

Critical Impact

Remote, unauthenticated attackers can access and modify device operations over ONVIF, compromising confidentiality, integrity, and availability of affected cameras.

Affected Products

  • Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4
  • ONVIF service endpoints exposed by the affected firmware
  • Deployments referenced in CISA ICS Advisory ICSA-26-272-05

Discovery Timeline

  • 2026-09-29 - CVE-2026-100291 published to the National Vulnerability Database
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-100291

Vulnerability Analysis

The Anjvision YSSD-RTMP-H5 device exposes ONVIF web service endpoints used for camera management, media configuration, and control operations. In firmware version 3.3.2.4, several of these endpoints accept and process management requests without validating client credentials. Any host able to reach the ONVIF service over the network can send Simple Object Access Protocol (SOAP) requests that alter device state or retrieve sensitive configuration.

Because ONVIF sits directly on top of HTTP, exploitation requires no user interaction and no prior foothold. An attacker on the same segment, or across the internet where the device is exposed, can iterate through unauthenticated methods and pivot to full device control. Impacted operations can include stream configuration, user management, and network settings depending on the endpoint invoked.

Root Cause

The root cause is a missing authentication check on ONVIF service handlers that should require WS-Security credentials. The firmware treats management endpoints as if they were public discovery endpoints, aligning with CWE-1188 style insecure defaults where a security control is absent by design rather than misconfigured by the operator.

Attack Vector

Exploitation occurs over the network with low complexity and no privileges. An attacker sends crafted SOAP requests to the ONVIF endpoints exposed by the camera and receives responses or effects state changes without supplying valid credentials. See the CISA ICS Advisory ICSA-26-272-05 for the vendor-coordinated technical description.

No verified public proof-of-concept code is available. The vulnerability mechanism is straightforward: unauthenticated SOAP calls to ONVIF management operations are accepted and processed by the device.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-100291

Indicators of Compromise

  • Unauthenticated HTTP POST requests to ONVIF service paths such as /onvif/device_service, /onvif/media_service, or /onvif/user_service from unexpected sources.
  • SOAP request bodies invoking methods like SetUser, CreateUsers, SetNetworkInterfaces, or SetSystemFactoryDefault without a wsse:Security header.
  • Unexpected changes to camera user accounts, RTSP stream URLs, or network configuration on YSSD-RTMP-H5 devices running firmware 3.3.2.4.

Detection Strategies

  • Inspect network traffic to and from ONVIF devices for SOAP requests missing WS-Security authentication headers.
  • Baseline expected ONVIF client IP addresses (video management systems) and alert on new sources issuing management calls.
  • Correlate camera reboots, factory resets, or configuration changes with preceding HTTP requests to ONVIF endpoints.

Monitoring Recommendations

  • Enable logging on network segments hosting IP cameras and forward flow and HTTP metadata to a central analytics platform.
  • Monitor for scanning activity targeting TCP ports typically used by ONVIF services (commonly 80, 8000, 8080, 2020).
  • Track firmware versions across the camera fleet and flag any device still running Anjvision YSSD-RTMP-H5 3.3.2.4.

How to Mitigate CVE-2026-100291

Immediate Actions Required

  • Restrict network reachability of affected cameras to trusted video management hosts only, using firewall or VLAN segmentation.
  • Remove any internet exposure of ONVIF endpoints on YSSD-RTMP-H5 devices.
  • Review camera user accounts and configuration for unauthorized changes and reset credentials on suspect devices.
  • Follow the guidance published in CISA ICS Advisory ICSA-26-272-05.

Patch Information

No vendor patch reference is included in the NVD entry at publication time. Consult the vendor and the CISA ICS Advisory ICSA-26-272-05 for updated firmware availability and coordinated remediation guidance.

Workarounds

  • Place affected cameras behind a dedicated management VLAN and block inbound ONVIF traffic from untrusted networks.
  • Terminate ONVIF traffic at an authenticating reverse proxy that enforces client authentication before forwarding SOAP requests to the device.
  • Disable ONVIF services on devices where they are not required for operational use.
  • Replace end-of-life or unpatchable devices with hardware that enforces authentication on all management interfaces.
bash
# Example: restrict ONVIF access to a trusted VMS host using iptables on an upstream gateway
iptables -A FORWARD -p tcp -s 10.20.30.40 -d 10.10.0.0/24 --dport 80 -j ACCEPT
iptables -A FORWARD -p tcp -d 10.10.0.0/24 --dport 80 -j DROP
iptables -A FORWARD -p tcp -d 10.10.0.0/24 --dport 8080 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.