compose-lint: `fix --apply` can delete a line the user did not select, including a security setting
- Exploited
- No known exploitation
- Fix
- Fixed in 0.18.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.18.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
compose-lint, a Docker Compose security linter, can delete a line the user did not select, including a security setting, when `fix --apply` runs on a file with a line-separator character inside a quoted value. An attacker can remotely, without logging in, submit a pull request containing that character, and the resulting Compose file can still be valid while the command reports a successful fix.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.9.0 until 0.18.0, compose-lint's YAML parser recognizes lone carriage returns and Unicode line separators U+0085, U+2028, and U+2029 as line breaks while fix position conversion counts only newline characters. A pull request can place one of these separators in a quoted value so fix --apply shifts each later edit and deletes the line after the selected target, including an unselected network or other security setting. The resulting Compose file can remain valid, post-edit checks can pass, and the command can report a successful fix even though the dry-run diff was the only place showing the extra deletion. This issue is fixed in version 0.18.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.18.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tmatens compose-lint
From 0.9.0 · fixed in 0.18.0
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123370
Is CVE-2026-123370 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123370?
compose-lint: from 0.9.0 before 0.18.0.Source: cve.now feed data
How do I fix CVE-2026-123370?
Upgrade to a fixed version: 0.18.0.Source: cve.now feed data