CVE-2026-123372

LOWPre-NVD 2.32.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-120129 (ENISA EUVD) · GHSA-jf3h-8jvx-vcrg (GitHub Security Advisories)Source: ENISA EUVD

2.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 2.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.22.0 until 0.32.0, compose-lint substitutes values from a sibling .env file into image fields and quotes the resolved value in CL-0004 and CL-0019 finding messages and fix text. In a workflow that writes secrets into that file and then lints untrusted pull-request content, an attacker can reference a secret variable so its whole value reaches the job log, JSON output, SARIF artifacts, and Code Scanning alerts. Fork pull requests normally lack secrets, so exploitation requires a secret-bearing workflow such as pull_request_target, same-repository branches, or a retained .env on a self-hosted runner, and the pass or fail result is unchanged. This issue is fixed in version 0.32.0.

CVSS
2.3
EG Score
2.3LOWmedium confidence
EG Risk
26
EG Risk 26/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)
Severity23% × 45%
Impact severity (EG Severity): CVSS 2.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
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 (2.3): severity, escalated by confirmed exploitation. This CVE's 2.3 is its impact severity (EG Severity), not escalated.

EG Severity
2.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: 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).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

November 9, 2026

Last Modified

November 13, 2026

References (4)

Vendor Advisories for CVE-2026-123372(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
actionstmatens/compose-lint @ 0.32.0 (fixes >= 0.22.0, <= 0.31.0)—ghsa
pipcompose-lint @ 0.32.0 (fixes >= 0.22.0, <= 0.31.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
GitHub Actions(1)
PackageVulnerable rangeFix by version rangeDependents
tmatens/compose-lintv0.31.0 ... v0.22.0 (10 versions)2d42617e4c6416f797bbfc6a057950131fa02df3 (one range)—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
compose-lint0.22.0 ... 0.31.0 (10 versions)
  • 0.22.0 up to 0.32.0: fixed in 0.32.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-13 13:29 UTCEchelonGraph re-scored
  3. 2026-11-13 13:29 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  4. 2026-11-13 12:42 UTCEchelonGraph re-scored
  5. 2026-11-13 12:42 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  6. 2026-11-13 12:32 UTCEchelonGraph re-scored
  7. 2026-11-13 12:32 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  8. 2026-11-12 22:32 UTCEchelonGraph re-scored
  9. 2026-11-12 22:32 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  10. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-11-11 08:29 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  13. 2026-11-10 17:14 UTCEchelonGraph re-scored
  14. 2026-11-10 17:14 UTCGHSA enrichmentGHSA-jf3h-8jvx-vcrg · GitHub severity LOW
  15. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-11-09 18:28 UTCEchelonGraph re-scored
  17. 2026-11-09 18:00 UTCENISA EUVD ID recordedEUVD-2026-120129 · Source: ENISA EUVD
  18. 2026-11-09 17:40 UTCEchelonGraph re-scoredFirst assessed: 2.3 LOW
  19. 2026-11-09 17:39 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-123372?
CVE-2026-123372 is a low-severity vulnerability; its CVE record was published on November 9, 2026. compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.22.0 until 0.32.0, compose-lint substitutes values from a sibling .env file into image fields and quotes the resolved value in CL-0004 and CL-0019 finding messages and fix text. In…
When was the CVE record for CVE-2026-123372 published?
The CVE record for CVE-2026-123372 was published on November 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-123372 actively exploited?
CVE-2026-123372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-123372?
CVE-2026-123372 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-123372?
A fix for CVE-2026-123372 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-123372 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-123372

Explore →

Is Your Infrastructure Affected by CVE-2026-123372?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs