Use of Hard-coded Credentials in Anjvision YSSD-RTMP-H5

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Anjvision/YSSD-RTMP-H5 (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Anjvision/YSSD-RTMP-H5.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 29, 2026

Sources and claim methodology

• CISA Known Exploited Vulnerabilities catalogcisa.gov

Related CVEs

• Initialization of a resource with an insecure default in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package
• Improper neutralization of special elements used in an OS command ('OS command injection') in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package
• Improper verification of cryptographic signature in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package
• Active debug code in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package
• Improper Check for Unusual or Exceptional Conditions in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package
• Server-Side request forgery (SSRF) in Anjvision YSSD-RTMP-H5Same anjvision/yssd-rtmp-h5 package