LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1502: HTTP client proxy tunnel headers not validated for CR/LF

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

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CPython’s http.client could accept carriage-return or line-feed characters in proxy tunnel headers or the host value. In affected applications, attacker-influenced values could alter the structure of an outbound proxy request, potentially compromising request integrity. The reported severity is medium, with material risk concentrated in applications that pass untrusted data into proxy-tunnel configuration.

Executive priority

Treat this as a targeted, moderate-priority remediation. Prioritize internet-facing or multi-tenant services that construct proxy tunnels from less-trusted input. Broad emergency action is not supported by the supplied evidence, but exposed applications should be reviewed promptly because successful abuse could compromise outbound request integrity.

Technical view

CVE-2026-1502 is a CWE-93 injection flaw caused by missing CR/LF validation in HTTP client proxy tunnel headers or host values. The CVSS 4.0 score is 5.7. The vector reports network reachability, low complexity, additional attack conditions, high privileges, passive user interaction, and high integrity impact without confidentiality or availability impact.

Likely exposure

Exposure is most likely where listed CPython versions use http.client proxy tunneling and allow attacker-controlled host or header values. The bundle lists 3.11.0, 3.12.0, 3.13.0, 3.14.0a1, and 3.15.0a1, but does not provide complete affected ranges or fixed release numbers.

Exploitation context

The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Exploitation requires specific application behavior and the conditions reflected by CVSS, including high privileges and passive user interaction. Public issue and patch references exist, but their presence alone does not establish exploitation.

Researcher notes

The supplied record identifies CWE-93 and multiple upstream commits, but omits exact fixed release numbers and complete affected version ranges. Validate branch applicability through the vendor advisory, issue, and pull request. Avoid concluding that all Python HTTP clients or all releases are vulnerable; the stated scope is CPython http.client proxy tunnel headers or host handling.

Mitigation direction

  • Review the Python security advisory and CPython issue for authoritative affected and fixed release details.
  • Update to an official CPython release incorporating the referenced fixes when vendor guidance confirms availability.
  • Prevent untrusted input from controlling proxy tunnel hosts or headers.
  • Reject carriage-return and line-feed characters before values reach proxy tunnel configuration.

Validation and detection

  • Inventory CPython versions and applications using http.client proxy tunneling.
  • Trace whether external or lower-trust data can influence tunnel hosts or headers.
  • Confirm installed builds include the applicable upstream patch or vendor-provided update.
  • Add defensive tests verifying prohibited control characters are rejected without sending network traffic.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-93: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1502 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N——PSF

Vulnerability scoring details

Base CVSS 4.0 score

5.7Medium
CVSS 4.0 vector shape for CVE-2026-1502Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Python Software FoundationCPythonhttp.client, 0, 3.11.0, 3.12.0, 3.13.0, 3.14.0a1, 3.15.0a1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-93 · source CWE mapping

Improper Neutralization of CRLF Sequences ('CRLF Injection')

Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.