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.2%CVSS: 6.1Exploit: None knownExposed services: Not assessed

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.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

Published

April 22, 2026

Last Modified

July 27, 2026

Advisory Details (6)

Auto-updated Jul 27, 2026
Patch available. 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 / EcosystemFix (by version range) / 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 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.11-1 ... 3.13.9-1 (7 versions)
  • every version up to 3.13.14-1: fixed in 3.13.14-1
—
python3.143.14.0-1 ... 3.14.4-2 (21 versions)
  • every version up to 3.14.5~rc1-1: fixed in 3.14.5~rc1-1
—
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 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: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
  • every version up to 3.13.5-2+deb13u2: fixed in 3.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 6× in last 7d / 22× 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 209 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.2% probability of exploitation in the next 30 days (10th percentile of EPSS-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?
A fix for CVE-2026-6019 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6019 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-6019

Explore →

Is Your Infrastructure Affected by CVE-2026-6019?

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

Book a Demo →Browse All CVEs