CVE-2026-123370

CVE-2026-123370 is a medium-severity security vulnerability in compose-lint (pip), affecting versions >= 0.9.0, <= 0.17.0. It is fixed in 0.18.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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].

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.

Affected versions

compose-lint (>= 0.9.0, <= 0.17.0)

Security releases

compose-lint → 0.18.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

  1. What is CVE-2026-123370? CVE-2026-123370 is a medium-severity security vulnerability in compose-lint (pip), affecting versions >= 0.9.0, <= 0.17.0. It is fixed in 0.18.0.
  2. Which versions of compose-lint are affected by CVE-2026-123370? compose-lint (pip) versions >= 0.9.0, <= 0.17.0 is affected.
  3. Is there a fix for CVE-2026-123370? Yes. CVE-2026-123370 is fixed in 0.18.0. Upgrade to this version or later.
  4. Is CVE-2026-123370 exploitable, and should I be worried? Whether CVE-2026-123370 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-123370 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-123370? Upgrade compose-lint to 0.18.0 or later.

Other vulnerabilities in compose-lint

Stop the waste.
Protect your environment with Kodem.