In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, the device includes a legacy password hash on the serial console that relies on a weak DES‑based encryption.
CVE-2026-100299
Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. A secondary CVSS source baseline 6.8; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.8
- EG Score
- 6.8MEDIUMhigh confidence
- EG Risk
- 31EG Risk 31/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 29, 2026
Last Modified
September 29, 2026
Advisory Details (1)
Auto-updated Sep 29, 2026Anjvision YSSD-RTMP-H5 | CISA
https://www.cisa.gov/news-events/ics-advisories/icsa-26-272-05Vendor Advisories for CVE-2026-100299(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-05 10:39 UTCGHSA enrichment
- 2026-10-04 12:38 UTCGHSA enrichment
- 2026-10-03 14:37 UTCEG score recompute
- 2026-10-03 14:36 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 16:34 UTCEG score recompute
- 2026-10-02 16:34 UTCGHSA enrichment
- 2026-10-01 18:32 UTCGHSA enrichment
- 2026-09-30 20:28 UTCEG score recompute
- 2026-09-30 20:28 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 22:26 UTCGHSA enrichment
- 2026-09-29 21:44 UTCEG score recompute
- 2026-09-29 21:44 UTCGHSA enrichment
- 2026-09-29 21:28 UTCEG score recompute
- 2026-09-29 20:22 UTCEG score recompute
- 2026-09-29 20:00 UTCEG score recompute
- 2026-09-29 19:58 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100299?
When was CVE-2026-100299 disclosed?
Is CVE-2026-100299 actively exploited?
What is the CVSS score of CVE-2026-100299?
How do I remediate CVE-2026-100299?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100299
Is Your Infrastructure Affected by CVE-2026-100299?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.