CVE-2016-5699

CVE-2016-5699 is a medium-severity vulnerability in Python with a CVSS 3.x base score of 6.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-113.

Key facts

Description

CRLF injection vulnerability in the HTTPConnection.putheader function in urllib2 and urllib in CPython (aka Python) before 2.7.10 and 3.x before 3.4.4 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in a URL.

Frequently asked questions

What is CVE-2016-5699?
CRLF injection vulnerability in the HTTPConnection.putheader function in urllib2 and urllib in CPython (aka Python) before 2.7.10 and 3.x before 3.4.4 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in a URL.
How severe is CVE-2016-5699?
CVE-2016-5699 has a CVSS 3.x base score of 6.1, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2016-5699 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 10% (95th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-5699?
CVE-2016-5699 primarily affects Python. In total, 27 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-5699?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-5699 published?
CVE-2016-5699 was published on 2016-09-02 and last updated on 2026-06-17.

References

Affected products (27)

More vulnerabilities in Python

All CVEs affecting Python →

Other CWE-113 (HTTP Response Splitting) vulnerabilities

Browse all CWE-113 (HTTP Response Splitting) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: