CVE-2026-1502

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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
Severity57% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

April 10, 2026

Last Modified

August 13, 2026

Advisory Details (6)

Auto-updated May 10, 2026
Patch available.
generic

oss-security - CPython [CVE-2026-1502] HTTP client proxy tunnel headers not validated for CR/LF

http://www.openwall.com/lists/oss-security/2026/04/11/4
generic

Mailman 3 [CVE-2026-1502] HTTP client proxy tunnel headers not validated for CR/LF - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/2IVPAEQWUJBCTQZEJEVTYCIKSMQPGRZ3/
generic

gh-146211: Reject CR/LF in HTTP tunnel request headers by sethmlarson · Pull Request #146212 · python/cpython · GitHub

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

HTTP proxy via "CONNECT" tunneling doesn't sanitize CR/LF · Issue #146211 · python/cpython · GitHub

https://github.com/python/cpython/issues/146211
generic

[3.14] gh-146211: Reject CR/LF in HTTP tunnel request headers (GH-146… · python/cpython@b1cf901 · GitHub

https://github.com/python/cpython/commit/b1cf9016335cb637c5a425032e8274a224f4b2ed
generic

gh-146211: Reject CR/LF in HTTP tunnel request headers (#146212) · python/cpython@05ed7ce · GitHub

https://github.com/python/cpython/commit/05ed7ce7ae9e17c23a04085b2539fe6d6d3cef69

Vendor Advisories for CVE-2026-1502(13)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatpython3.14-0:3.14.4-2.el10_22026-05-19redhat
redhatpython3.12-0:3.12.13-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el10_22026-05-19redhat
redhatpython3.14-0:3.14.4-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el8_102026-04-27redhat
redhatpython3-13-main-3.13.13-1.1.hum12026-04-23redhat
redhatpython3-14-main-3.14.4-2.hum12026-04-21redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat

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

(13 across 7 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.21+dfsg-4 (9 versions)
  • every version up to 7.3.22+dfsg-1: fixed in 7.3.22+dfsg-1
—
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.5~rc1-1 (22 versions)
  • every version up to 3.14.5-1: fixed in 3.14.5-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
  • every version up to 3.13.5-2+deb13u3: fixed in 3.13.5-2+deb13u3
—
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
—

Weakness Classification(1)

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 / 20× 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 222 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-1502?
CVE-2026-1502 is a medium vulnerability published on April 10, 2026. CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
When was CVE-2026-1502 disclosed?
CVE-2026-1502 was first published on April 10, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1502 actively exploited?
CVE-2026-1502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1502?
CVE-2026-1502 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-1502?
A fix for CVE-2026-1502 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-1502 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-1502

Explore →

Is Your Infrastructure Affected by CVE-2026-1502?

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

Book a Demo →Browse All CVEs