compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. Prior to 0.31.0, compose-lint prints attacker-controlled service names, environment keys, file lines, and other Compose text without neutralizing GitHub Actions and Azure Pipelines workflow-command openers. When a workflow processes a pull request, legacy ##[ commands or a line-leading double-colon command can create false annotations, hide log regions, mask selected strings, or invoke other commands recognized by the runner. The affected text report paths do not alter the compose-lint exit code or pass or fail result, but they can misrepresent the CI output presented to reviewers. This issue is fixed in version 0.31.0.
CVE-2026-123369
MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-11-10) is not newer than that change (2026-11-12), so it does not.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-120126 (ENISA EUVD) · GHSA-6f4g-xm8v-pgv6 (GitHub Security Advisories)Source: ENISA EUVD
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 24EG Risk 24/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)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 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 every mission impact level.Exploitation none (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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-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 every mission impact level.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 every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (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 12, 2026
Advisory Details (4)
Auto-updated Nov 9, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available
v0.31.0
Patch available: tmatens/compose-lint v0.31.0
https://github.com/tmatens/compose-lint/releases/tag/v0.31.0GitHub commit
commit 672bd1114562 (tmatens/compose-lint)
Fix landed in tmatens/compose-lint commit 672bd1114562 — awaiting tagged release
https://github.com/tmatens/compose-lint/commit/672bd11145621f787c295fb11f3a859cdec1b38dGitHub pull request
Stop Compose file text from issuing CI workflow commands
Fix merged in tmatens/compose-lint PR #918 on 2026-09-27 — awaiting tagged release
https://github.com/tmatens/compose-lint/pull/918GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Compose file text can issue GitHub Actions workflow commands through the compose-lint Action · Advisory · tmatens/compose-lint · GitHub
Affected: 0.31.0. The Action stops the runner from processing workflow commands while compo
https://github.com/tmatens/compose-lint/security/advisories/GHSA-6f4g-xm8v-pgv6Vendor Advisories for CVE-2026-123369(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 / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| actions | tmatens/compose-lint @ 0.31.0 (fixes >= 0.2.0, <= 0.30.0) | — | ghsa |
| pip | compose-lint @ 0.31.0 (fixes <= 0.30.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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tmatens/compose-lint | v0.30.0 ... v0.2.0 (44 versions) | a6a7a76736de1c72abfa96c41ff8af556ffdc55f (one range) | — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| compose-lint | 0.10.0 ... 0.9.0 (44 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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.
- 2026-11-12 22:31 UTCEchelonGraph re-scored▲ 1.00
- 2026-11-12 22:31 UTCGHSA enrichmentGHSA-6f4g-xm8v-pgv6 · GitHub severity MODERATE · GitHub CVSS 4.3
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-11 07:27 UTCGHSA enrichmentGHSA-6f4g-xm8v-pgv6 · GitHub severity MODERATE · GitHub CVSS 4.3
- 2026-11-10 17:14 UTCEchelonGraph re-scored▼ 1.00
- 2026-11-10 17:14 UTCGHSA enrichmentGHSA-6f4g-xm8v-pgv6 · GitHub severity MODERATE · GitHub CVSS 4.3
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-09 23:48 UTCEchelonGraph re-scored
- 2026-11-09 23:05 UTCEchelonGraph re-scored
- 2026-11-09 18:27 UTCEchelonGraph re-scored
- 2026-11-09 18:00 UTCENISA EUVD ID recordedEUVD-2026-120126 · Source: ENISA EUVD
- 2026-11-09 17:40 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
- 2026-11-09 17:39 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
9 shownGitHub Actions:tmatens/compose-lint · PyPI:compose-lint
Frequently asked(5)
What is CVE-2026-123369?
CVE-2026-123369 is a medium-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. Prior to 0.31.0, compose-lint prints attacker-controlled service names, environment keys, file lines, and other Compose text without neutralizing GitHub Actions and Azure Pipelines…
When was the CVE record for CVE-2026-123369 published?
The CVE record for CVE-2026-123369 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-123369 actively exploited?
CVE-2026-123369 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-123369?
CVE-2026-123369 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-123369?
A fix for CVE-2026-123369 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-123369 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-123369
Is Your Infrastructure Affected by CVE-2026-123369?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.