ZoneMinder is a free, open source closed-circuit television software application. Prior to 1.38.3, downloadEvents() manually wraps a monitor Name value in single quotes instead of using escapeshellarg() before placing it in shell commands when a user with monitor-create or monitor-edit permission stores a monitor Name containing shell metacharacters and a user with Events View permission exports that monitor's events. In this attack mechanism, the stored monitor Name reaches both the ffmpeg concatenation command and the tar or zip archive command and breaks out of manual quoting. Arbitrary commands execute as the web server user. This issue is fixed in version 1.38.3.
CVE-2026-102608
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-16. A secondary CVSS source baseline 9.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
The CVE record names the fixed release — apply it.
- CVSS v3
- 9.0
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity90% × 45%Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: The CVE record names the fixed release. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 20th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
The CVE record names the fixed release. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 16, 2026
Last Modified
October 19, 2026
Advisory Details (5)
Auto-updated Oct 16, 2026Two Sinks, One Shell: OS Command Injection in ZoneMinder — scriptkittens
https://www.scriptkittens.com/blog/two-sinks-one-shellcommit b5605e01c143 (ZoneMinder/zoneminder)
Fix landed in ZoneMinder/zoneminder commit b5605e01c143 — awaiting tagged release
https://github.com/ZoneMinder/zoneminder/commit/b5605e01c14354fc8e2dcae8cefd90c3674880d9commit b3a7c05f079c (ZoneMinder/zoneminder)
Fix landed in ZoneMinder/zoneminder commit b3a7c05f079c — awaiting tagged release
https://github.com/ZoneMinder/zoneminder/commit/b3a7c05f079c87badf4b0ce052da0acfd4047a4bcommit 2de2ae44a1d7 (ZoneMinder/zoneminder)
Fix landed in ZoneMinder/zoneminder commit 2de2ae44a1d7 — awaiting tagged release
https://github.com/ZoneMinder/zoneminder/commit/2de2ae44a1d751bad4b020c5573b2d58c59c1525[High] Authenticated OS Command Injection via unsanitized Monitor Name in event export (download_functions.php) · Advisory · ZoneMinder/zoneminder · GitHub
https://github.com/ZoneMinder/zoneminder/security/advisories/GHSA-88m4-hrgp-m9v3Vendor Advisories for CVE-2026-102608(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 19× in last 7d / 19× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-20 19:45 UTCEG score recompute
- 2026-10-20 19:45 UTCGHSA enrichmentGHSA-v9cj-6fp2-33q4 · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-19 17:29 UTCEG score recompute
- 2026-10-19 17:29 UTCGHSA enrichmentGHSA-v9cj-6fp2-33q4 · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-19 16:49 UTCEG score recompute
- 2026-10-19 16:48 UTCGHSA enrichmentGHSA-v9cj-6fp2-33q4 · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-19 01:00 UTCEG score recompute
- 2026-10-19 01:00 UTCGHSA enrichmentGHSA-v9cj-6fp2-33q4 · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-18 05:10 UTCEG score recompute
- 2026-10-17 22:45 UTCEG score recompute
- 2026-10-17 22:44 UTCGHSA enrichmentGHSA-v9cj-6fp2-33q4 · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-16 20:27 UTCEG score recompute
- 2026-10-16 19:38 UTCEG score recomputeFirst assessed: 9.0 CRITICAL
- 2026-10-16 19:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
Frequently asked(5)
What is CVE-2026-102608?
When was the CVE record for CVE-2026-102608 published?
Is CVE-2026-102608 actively exploited?
What is the CVSS score of CVE-2026-102608?
How do I remediate CVE-2026-102608?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-102608
Is Your Infrastructure Affected by CVE-2026-102608?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.