CVE-2026-6019

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory (severity: LOW) published 2026-04-22. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

http.cookies.Morsel.js_output() returns an inline snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 27, 2026

Advisory Details (6)

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

Mailman 3 [CVE-2026-6019] BaseCookie.js_output() does not neutralize characters in cookie value embedded in JS - Security-announce - python.org

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

gh-90309: Base64-encode cookie values embedded in JS

Fix merged in python/cpython PR #148848 on 2026-04-22 — awaiting tagged release

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

SimpleCookie.js_output is vulnerable to HTML injection · Issue #90309 · python/cpython · GitHub

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

commit f795e042043d (python/cpython)

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

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

commit 76b3923d688c (python/cpython)

Fix landed in python/cpython commit 76b3923d688c — awaiting tagged release

https://github.com/python/cpython/commit/76b3923d688c0efc580658476c5f525ec8735104
github_commit

commit 3c59b8b53fc7 (python/cpython)

Fix landed in python/cpython commit 3c59b8b53fc7 — awaiting tagged release

https://github.com/python/cpython/commit/3c59b8b53fc75c7f9578d16fb8201ceb43e8f76c

Vendor Advisories for CVE-2026-6019(10)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.14-venv (3.14.4-1ubuntu0.1) @ resolute2026-07-27ubuntu
redhatpython3-11-main-3.11.15-4.3.hum12026-06-30redhat
redhatpython3-12-main-3.12.13-3.2.hum12026-06-29redhat
redhatpython3-13-main-3.13.14-1.1.hum12026-06-29redhat
redhatpython3.14-0:3.14.5-1.el10_22026-06-24redhat
redhatpython3.14-0:3.14.5-1.el9_82026-06-23redhat
redhatpython3-14-main-3.14.5-2.hum12026-06-03redhat

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.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (7 versions)3.13.14-1—
python3.143.14.0-1 ... 3.14.4-2 (21 versions)3.14.5~rc1-1—
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python3.93.9.10-1 ... 3.9.9-4 (29 versions)——
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.9-1 (28 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-2, 3.13.5-2+deb13u13.13.5-2+deb13u2—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 5× in last 7d / 63× 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 175 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6019?
CVE-2026-6019 is a medium vulnerability published on April 22, 2026. http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie…
When was CVE-2026-6019 disclosed?
CVE-2026-6019 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6019 actively exploited?
CVE-2026-6019 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 86.5% of all scored CVEs.
What is the CVSS score of CVE-2026-6019?
CVE-2026-6019 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-6019?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6019, 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-6019

Explore →

Is Your Infrastructure Affected by CVE-2026-6019?

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

Start Free Scan →Browse All CVEs