CVE-2026-0864

MEDIUMPre-NVD 4.14.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When using the "configparser" module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.

CVSS v3
4.1
EG Score
4.1(medium)
EPSS
2.8%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 25, 2026

Advisory Details (7)

Auto-updated Jun 25, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Mailman 3 [CVE-2026-0864] Configparser newline injection in write() method - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/CV4NE6AFCRJL7XQOHX7J5TSDHUWVWGJS/
github_pr

gh-151558: Fix symlink escape via `tarfile` hardlink-extraction fallback

Fix merged in python/cpython PR #151559 on 2026-06-23 — awaiting tagged release

https://github.com/python/cpython/pull/151559
generic

Normalize all line ending (CR, CRLF, and LF) to LF+TAB in configparser · Issue #143927 · python/cpython · GitHub

https://github.com/python/cpython/issues/143927
github_commit

commit aaf850fd333c (python/cpython)

Fix landed in python/cpython commit aaf850fd333c — awaiting tagged release

https://github.com/python/cpython/commit/aaf850fd333cd89e9aada03d92aaa788a6cb1bb8
github_commit

commit 71f2e02a52d4 (python/cpython)

Fix landed in python/cpython commit 71f2e02a52d4 — awaiting tagged release

https://github.com/python/cpython/commit/71f2e02a52d47417a6fd69f456346cd8aa7aca98
github_commit

commit 5858e42c539d (python/cpython)

Fix landed in python/cpython commit 5858e42c539d — awaiting tagged release

https://github.com/python/cpython/commit/5858e42c539dac8394636a6e9b30472b8994851f
github_commit

commit 0adb386f6e68 (python/cpython)

Fix landed in python/cpython commit 0adb386f6e68 — awaiting tagged release

https://github.com/python/cpython/commit/0adb386f6e68eb2e73d32e19f235d012df009528

Vendor Advisories for CVE-2026-0864(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 20:52 UTCEG score recompute
  2. 2026-07-06 20:52 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 20:42 UTCEG score recompute
  6. 2026-07-05 20:42 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 20:36 UTCEG score recompute
  10. 2026-07-04 20:36 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 20:29 UTCEG score recompute
  13. 2026-07-03 20:29 UTCGHSA enrichment
  14. 2026-07-02 20:24 UTCEG score recompute
  15. 2026-07-02 20:24 UTCGHSA enrichment
  16. 2026-07-01 20:19 UTCEG score recompute
  17. 2026-07-01 20:19 UTCGHSA enrichment
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 20:14 UTCEG score recompute
  20. 2026-06-30 20:14 UTCGHSA enrichment
  21. 2026-06-29 20:08 UTCEG score recompute
  22. 2026-06-29 20:08 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 20:02 UTCEG score recompute
  25. 2026-06-28 20:02 UTCGHSA enrichment
Show 19 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 19:57 UTCEG score recompute
  5. 2026-06-27 19:57 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 19:52 UTCEG score recompute
  8. 2026-06-26 19:52 UTCGHSA enrichment
  9. 2026-06-25 19:47 UTCEG score recompute
  10. 2026-06-25 19:47 UTCGHSA enrichment
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 19:42 UTCEG score recompute
  13. 2026-06-24 19:41 UTCGHSA enrichment
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 19:35 UTCEG score recompute▲ 4.10
  16. 2026-06-23 19:34 UTCGHSA enrichment
  17. 2026-06-23 19:32 UTCNVD updateCVSS v3 → 4.1 · CVSS v4 → 4.1
  18. 2026-06-23 19:21 UTCEG score recompute
  19. 2026-06-23 19:21 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0864?
CVE-2026-0864 is a medium vulnerability published on June 23, 2026. When using the "configparser" module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.
When was CVE-2026-0864 disclosed?
CVE-2026-0864 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0864 actively exploited?
CVE-2026-0864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0864?
CVE-2026-0864 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2026-0864?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0864, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0864

Explore →

Is Your Infrastructure Affected by CVE-2026-0864?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs