CVE-2026-0672

MEDIUMNVD 6.06.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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, nvd
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

A fix is available — apply it.

When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

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
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

January 20, 2026

Last Modified

June 17, 2026

Advisory Details (9)

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

Mailman 3 [CVE-2026-0672] Header injection in http.cookies.Morsel - Security-announce - python.org

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

gh-143919: Reject control characters in http cookies

Fix merged in python/cpython PR #143920 on 2026-01-20 — awaiting tagged release

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

Reject control characters in http.cookies.Morsel · Issue #143919 · python/cpython · GitHub

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

commit b1869ff648bb (python/cpython)

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

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

commit 95746b3a13a9 (python/cpython)

Fix landed in python/cpython commit 95746b3a13a9 — awaiting tagged release

https://github.com/python/cpython/commit/95746b3a13a985787ef53b977129041971ed7f70
github_commit

commit 918387e4912d (python/cpython)

Fix landed in python/cpython commit 918387e4912d — awaiting tagged release

https://github.com/python/cpython/commit/918387e4912d12ffc166c8f2a38df92b6ec756ca
github_commit

commit 7852d72b653f (python/cpython)

Fix landed in python/cpython commit 7852d72b653f — awaiting tagged release

https://github.com/python/cpython/commit/7852d72b653fea0199acf5fc2a84f6f8b84eba8d
github_commit

commit 712452e6f1d4 (python/cpython)

Fix landed in python/cpython commit 712452e6f1d4 — awaiting tagged release

https://github.com/python/cpython/commit/712452e6f1d4b9f7f8c4c92ebfcaac1705faa440
github_commit

commit 62700107418e (python/cpython)

Fix landed in python/cpython commit 62700107418e — awaiting tagged release

https://github.com/python/cpython/commit/62700107418eb2cca3fc88da036a243ea975f172

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.11-venv (3.11.0~rc1-1~22.04.1~esm8) @ jammy2026-06-08ubuntu
ubuntupython2.7-minimal (2.7.12-1ubuntu0~16.04.18+esm19) @ xenial2026-06-08ubuntu
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatpython3.12-0:3.12.13-2.el10_22026-05-19redhat
redhatpython3.12-0:3.12.13-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el8_102026-04-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 4 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2, 7.3.20+dfsg-1, 7.3.20+dfsg-2, 7.3.20+dfsg-3, 7.3.20+dfsg-47.3.21+dfsg-1
python3.133.13.11-1 ... 3.13.9-1 (6 versions)3.13.12-1
python3.143.14.0-1 ... 3.14.2-1 (14 versions)3.14.3-1
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u2, 3.9.2-1+deb11u3, 3.9.2-1+deb11u43.9.2-1+deb11u5
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)
python3.113.11.2-6 ... 3.11.2-6+deb12u6 (7 versions)3.11.2-6+deb12u7
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)
python3.133.13.5-23.13.5-2+deb13u1

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 41× 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.

Showing the most recent 100 of 158 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-0672?
CVE-2026-0672 is a medium vulnerability published on January 20, 2026. When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.
When was CVE-2026-0672 disclosed?
CVE-2026-0672 was first published in the National Vulnerability Database on January 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0672 actively exploited?
CVE-2026-0672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0672?
CVE-2026-0672 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-0672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0672, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0672

Explore →

Is Your Infrastructure Affected by CVE-2026-0672?

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