CVE-2026-0864

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2026-06-23. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 23, 2026

Last Modified

August 18, 2026

Advisory Details (7)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github_pr.
Web page

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 pull request

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
Web page

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.

Affected Packages

(14 across 8 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
  • every version on: no fix on record
—
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
  • every version on: no fix on record
—
python3.93.9.10-1 ... 3.9.9-4 (29 versions)
  • every version on: no fix on record
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-2 (12 versions)
  • every version up to 8.0.0+dfsg-1: fixed in 8.0.0+dfsg-1
—
python3.133.13.11-1 ... 3.13.9-1 (8 versions)
  • every version up to 3.13.15-1: fixed in 3.13.15-1
—
python3.143.14.0-1 ... 3.14.6-1 (24 versions)
  • every version up to 3.14.7-1: fixed in 3.14.7-1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.11+dfsg-2 ... 8.0.0+dfsg-1 (31 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.9-1 (28 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version on: no fix on record
—
python3.133.13.5-2, 3.13.5-2+deb13u1, 3.13.5-2+deb13u2, 3.13.5-2+deb13u3, 3.13.5-2+deb13u4
  • every version up to 3.13.5-2+deb13u5: fixed in 3.13.5-2+deb13u5
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.7-r0: fixed in 3.14.7-r0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 220 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 06:54 UTCOSV refresh
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 16:42 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-11 20:17 UTCEG score recompute
  6. 2026-10-11 18:29 UTCEG score recompute
  7. 2026-10-11 15:03 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-23 12:00 UTCEG score recompute
  24. 2026-09-23 12:00 UTCVendor advisory
  25. 2026-09-23 12:00 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
Show 75 more
  1. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-09-18 10:23 UTCEG score recompute
  4. 2026-09-18 10:23 UTCVendor advisory
  5. 2026-09-18 10:23 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  6. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-09-13 12:21 UTCEG score recompute
  9. 2026-09-13 12:21 UTCVendor advisory
  10. 2026-09-13 12:21 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  11. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-08-30 20:25 UTCEG score recompute
  22. 2026-08-30 20:25 UTCVendor advisory
  23. 2026-08-30 20:25 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-08-24 13:59 UTCEG score recompute
  30. 2026-08-24 13:59 UTCVendor advisory
  31. 2026-08-24 13:59 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  32. 2026-08-23 13:53 UTCEG score recompute
  33. 2026-08-23 13:53 UTCVendor advisory
  34. 2026-08-23 13:53 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  35. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-22 13:46 UTCEG score recompute
  37. 2026-08-22 13:46 UTCVendor advisory
  38. 2026-08-22 13:46 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  39. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-21 07:51 UTCEG score recompute
  41. 2026-08-21 07:51 UTCVendor advisory
  42. 2026-08-21 07:51 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  43. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-20 07:45 UTCEG score recompute
  45. 2026-08-20 07:45 UTCVendor advisory
  46. 2026-08-20 07:45 UTCGHSA enrichmentGHSA-g345-7jg6-m22p · GitHub CVSS 5.5
  47. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-18 18:05 UTCEG score recompute▲ 1.40
  49. 2026-08-18 18:05 UTCVendor advisory
  50. 2026-08-18 18:05 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  51. 2026-08-18 18:01 UTCNVD updateCVSS v3 → 5.5
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-17 01:44 UTCEG score recompute
  54. 2026-08-17 01:44 UTCVendor advisory
  55. 2026-08-17 01:44 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-16 01:39 UTCVendor advisory
  59. 2026-08-16 01:39 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  60. 2026-08-15 01:33 UTCEG score recompute
  61. 2026-08-15 01:33 UTCVendor advisory
  62. 2026-08-15 01:33 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  63. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-14 01:28 UTCEG score recompute
  65. 2026-08-14 01:28 UTCVendor advisory
  66. 2026-08-14 01:28 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  67. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-13 01:23 UTCEG score recompute
  69. 2026-08-13 01:23 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  70. 2026-08-13 00:41 UTCEG score recompute
  71. 2026-08-13 00:41 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  72. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-08-12 01:27 UTCEG score recompute
  74. 2026-08-12 01:27 UTCGHSA enrichmentGHSA-g345-7jg6-m22p
  75. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-0864?
CVE-2026-0864 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-0864 published?
The CVE record for CVE-2026-0864 was published on June 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 18, 2026; the record at its source may have been updated since.
Is CVE-2026-0864 actively exploited?
CVE-2026-0864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0864?
CVE-2026-0864 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-0864?
A fix for CVE-2026-0864 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-0864 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs