CVE-2026-123370: compose-lint: `fix --apply` can delete a line the user did not select, including a security setting
Impact compose-lint fix --apply converts the line numbers its fixers work with into positions in the file. The YAML parser treats a lone carriage return, U+0085, U+2028 and U+2029 as line breaks, but the conversion counted only \n. One of those characters inside a quoted value, which most editors and diff views don't show, shifted every later edit down by one line.
Published Nov 10, 2026
Affected packages
compose-lint
- Ecosystem
- PyPI
- Affected
- >= 0.9.0, <= 0.17.0
- Fixed in
- 0.18.0
- Check
pip show compose-lint
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
compose-lint fix --apply converts the line numbers its fixers work with into positions in the file. The YAML parser treats a lone carriage return, U+0085, U+2028 and U+2029 as line breaks, but the conversion counted only \n. One of those characters inside a quoted value, which most editors and diff views don't show, shifted every later edit down by one line.
A Compose file from a pull request can use this to make a fix delete the line after the one it meant to change. For example, fixing CL-0014 (logging: driver: none) instead removes driver: none and the following networks: [internal], moving the service off an internal-only network onto the default bridge. The result is still valid Compose, every check fix runs after editing passes, and the command reports applied 1 fix(es) and exits 0. A later compose-lint check passes too, because no rule requires networks:. The dry-run diff (without --apply) does show the removed lines, but --apply prints only the note for the fix that was selected.
A related crash on the same files could empty the SARIF output for every file in the run. GitHub Code Scanning rejects an empty SARIF upload, which fails the step, so that part does not report a false clean result there.
Found during an internal pre-1.0 security review.
Docker image. composelint/compose-lint tags 0.9.0 through 0.17.0, and the matching minor tags, are affected when used to run fix --apply. Fixed from 0.18.0.
The GitHub Action does not run fix and is not affected.
Patches
Fixed in 0.18.0. Line splitting and position conversion now share one definition of a line break, so they can't disagree. A Compose file containing an ambiguous line break (a lone \r, U+0085, U+2028 or U+2029) is refused with exit code 2, because no line numbering is correct for both the parser and the editor. CRLF and LF files are unaffected.
Workarounds
- Upgrade to 0.18.0 or later.
- On older versions, review the dry-run diff before
--apply, and don't runfix --applyover files from untrusted pull requests.
Reproduction
services:
web:
image: nginx@sha256:<digest>
labels:
note: "line oneline two"
logging:
driver: none
networks: [internal]
networks:
internal:
internal: truecompose-lint fix --apply compose.yml on 0.17.0 reports applied 1 fix(es), exits 0, and removes both driver: none and networks: [internal].
References
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-65v8-q222-64xx
- https://nvd.nist.gov/vuln/detail/CVE-2026-123370
- https://github.com/tmatens/compose-lint/pull/547
- https://github.com/tmatens/compose-lint/pull/549
- https://github.com/tmatens/compose-lint/commit/c9d453a6a69c076788fe1db05cb54684a616d1de
- https://github.com/tmatens/compose-lint/commit/cbbf886d91347dea9c51b584eb50088e70007d0d
- https://github.com/tmatens/compose-lint/releases/tag/v0.18.0
- https://github.com/advisories/GHSA-65v8-q222-64xx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-123368
compose-lint: .env read through a symlink outside the project can expose the CI job's environment
low3.1Nov 10, 2026CVE-2026-123369
compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action
medium4.3Nov 10, 2026CVE-2026-123371
compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target
low2.3Nov 10, 2026CVE-2026-123372
compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
low2.3Nov 10, 2026CVE-2026-123373
compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output
low2.3Nov 10, 2026CVE-2026-123796
compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`
low2.3Nov 10, 2026
