CVE-2026-1502

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 93% 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: cna:psf, epss
5.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.7Exploit: NoneExposed: 0

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.7(medium)
EPSS
42.8%
KEV
Not listed

Published

April 10, 2026

Last Modified

June 30, 2026

Advisory Details (6)

Auto-updated May 10, 2026
No patch confirmed yet.
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(12)

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 / EcosystemFixed in / 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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 110 total refreshes for this CVE.

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

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 in the National Vulnerability Database on April 10, 2026, with the most recent update on June 30, 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 42.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-1502?
CVE-2026-1502 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-1502?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1502, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs