Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

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

CVE-2026-123370GHSA-65v8-q222-64xx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (compose-lint 0.18.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source
EPSS
  • CVE-2026-123370: 0.33% estimated exploitation activity in the next 30 days; percentile 26.43 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-65v8-q222-64xx

  2. Revision 1 · created ·

    Published from ghsa record GHSA-65v8-q222-64xx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-123370

Advisory: compose-lint: `fix --apply` can delete a line the user did not select, including a security setting
IDs: CVE-2026-123370, GHSA-65v8-q222-64xx
Record: https://patchnext.com/advisories/cve-2026-123370 (revision 2, source checked 11 Nov 2026, 07:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: compose-lint 0.18.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI compose-lint: affected >= 0.9.0, < 0.18.0; fixed in 0.18.0

## Suggested inspection (read-only)
- `python -m pip show compose-lint`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on compose-lint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-65v8-q222-64xx (GitHub-reviewed advisory GHSA-65v8-q222-64xx lists affected ranges: PyPI compose-lint >=0.9.0 <=0.17.0)
- Verified: https://osv.dev/vulnerability/GHSA-65v8-q222-64xx (OSV record GHSA-65v8-q222-64xx lists affected ranges: PyPI compose-lint >=0.9.0 <0.18.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…