NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍 PyPI
Not in CISA KEV

CVE-2026-123370 — compose-lint

Fix: tmatens/compose-lint@c9d453a

CVE-2026-123370 is a CWE-193 vulnerability in compose-lint. A fix is available for compose-lint — see the affected versions and patch details below.

compose-lint: `fix --apply` can delete a line the user did not select, including a security setting

Also known asGHSA-65v8-q222-64xx
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🐍compose-lint

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 run fix --apply over files from untrusted pull requests.

Reproduction

services:
  web:
    image: nginx@sha256:<digest>
    labels:
      note: "line one<U+2028>line two"
    logging:
      driver: none
    networks: [internal]
networks:
  internal:
    internal: true

compose-lint fix --apply compose.yml on 0.17.0 reports applied 1 fix(es), exits 0, and removes both driver: none and networks: [internal].

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIcompose-lint≥ 0.9.0&&< 0.18.00.18.0pip install --upgrade 'compose-lint==0.18.0'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for compose-lint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update compose-lint to 0.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-123370 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 `networ
O3 Security · Impact-Aware SCA

Is CVE-2026-123370 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-123370: compose-lint — Fixed in 0.18.0