CVE-2026-123370
Medium 5.1No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 27% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-193
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/tmatens/compose-lint/commit/c9d453a6a69c076788fe1db05cb54684a616d1de (opens in a new tab)
- https://github.com/tmatens/compose-lint/commit/cbbf886d91347dea9c51b584eb50088e70007d0d (opens in a new tab)
- https://github.com/tmatens/compose-lint/pull/547 (opens in a new tab)
- https://github.com/tmatens/compose-lint/pull/549 (opens in a new tab)
- https://github.com/tmatens/compose-lint/releases/tag/v0.18.0 (opens in a new tab)
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-65v8-q222-64xx (opens in a new tab)