LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26116: http.client in Python 3.x before 3.5.10, 3.6.x before 3.6.12, 3.7.x before 3.7.9, and 3.8.x before 3.8.5 al...

http.client in Python 3.x before 3.5.10, 3.6.x before 3.6.12, 3.7.x before 3.7.9, and 3.8.x before 3.8.5 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of HTTPConnection.request.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Some Python versions allowed a malicious value used as the HTTP method to insert line breaks into an outgoing HTTP request. Business risk depends on whether applications let external users influence that method. This is not a broad remote takeover issue by itself, but it can corrupt requests or affect downstream HTTP handling in exposed services. Exposure is likely limited to applications running affected Python versions that use http.client and let untrusted input choose the HTTP method. Standard fixed-method clients are less likely exposed. Asset owners should also check distributor advisories because Fedora, Ubuntu, Debian, Gentoo, openSUSE, Oracle, and NetApp published related notices. Treat as a targeted dependency remediation item, not an emergency by default. Prioritize systems where user input can influence outbound HTTP requests, especially internet-facing automation, proxies, integrations, or security-sensitive internal services. Mitigation focus: Upgrade Python to fixed upstream versions or vendor-supported patched packages.; Prioritize internet-facing services that make outbound HTTP requests from user-controlled workflows.; Reject CR, LF, and unexpected method values before calling HTTP client libraries..

Prepared

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.

cve · low confidence lookup

CVE-2020-26116 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
14Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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