LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0865: wsgiref.headers.Headers allows header newline injection

User-controlled header names and values containing newlines can allow injecting HTTP headers.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Python standard library issue where unsafe newline characters in HTTP header names or values can let an attacker add unintended headers. It matters mainly for applications that build headers from user-controlled input using wsgiref.headers.Headers. It is not listed as actively exploited in the provided sources.

Executive priority

Handle as a normal security update with targeted urgency. Prioritize internet-facing or partner-facing Python services that construct HTTP headers from external input. This is not supported as an emergency zero-day by the provided sources.

Technical view

CVE-2026-0865 affects CPython’s wsgiref.headers.Headers. User-controlled header names or values containing newlines may enable HTTP header injection. The CVE maps to CWE-74 and has CVSS 4.0 score 5.9. The vector indicates network reachability, low attack complexity, attack prerequisites, high privileges, and high integrity impact.

Likely exposure

Exposure is limited to CPython environments using wsgiref.headers.Headers where untrusted input can influence HTTP header names or values. The source bundle lists CPython 3.11.0, 3.12.0, 3.13.0, 3.14.0, and 3.15.0a1 as affected entries, with other versions not clearly detailed.

Exploitation context

The provided data does not show CISA KEV listing or confirmed active exploitation. CVSS indicates exploitation requires high privileges and an attack prerequisite, reducing broad internet-scale risk. Successful abuse could affect HTTP response integrity by inserting unexpected headers.

Researcher notes

The bundle provides official CVE data, a PSF advisory, issue tracking, PR, and patch commits. It does not provide exact fixed release numbers in the structured fields. Validate final remediation against the PSF advisory and downstream package maintainers before closing findings.

Mitigation direction

  • Review the Python security advisory and your distribution’s Python package guidance.
  • Upgrade CPython to a vendor-fixed build containing the referenced patches.
  • Prioritize systems where wsgiref.headers.Headers processes untrusted header data.
  • Avoid passing newline-containing untrusted input into HTTP header names or values.
  • Track vendor backports if using OS-packaged Python.

Validation and detection

  • Inventory CPython versions across applications, containers, and build images.
  • Search codebases for use of wsgiref.headers.Headers.
  • Confirm whether header names or values can include user-controlled input.
  • Verify installed Python packages include the vendor security fix or backport.
  • Document exceptions where the vulnerable API is unreachable or trusted-only.
Prepared
Confidence
medium
Sources
6

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-74: 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-0865 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.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/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
0Timeline events
0ADP providers
16Source links

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.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

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

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Python Software FoundationCPython0, 3.11.0, 3.12.0, 3.13.0, 3.14.0, 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-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.