Skip to main content
No exploitation reportedFix available

CVE-2020-7695

No exploitation reported by the sources we read.

  • Published2020-07-27
  • Fixed in0.11.7
  • WeaknessCWE-74

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.

Timeline

dates in UTC
  1. 2020-07-2712:15CVE publishedNVD

Versions per branch

NVD · OSV
Encode uvicorn
BranchAffectedFixed in
0.11< 0.11.70.11.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • python-uvicornUbuntu:26.10all versions · no fixed version listed
  • python-uvicornUbuntu:26.04:LTSall versions · no fixed version listed
  • python-uvicornUbuntu:25.10all versions · no fixed version listed
  • python-uvicornUbuntu:24.04:LTSall versions · no fixed version listed
  • python-uvicornUbuntu:22.04:LTSall versions · no fixed version listed
  • python-uvicornUbuntu:20.04:LTSall versions · no fixed version listed
  • python-uvicornDebian:14all versions · fixed in 0.13.3-1
  • python-uvicornDebian:13all versions · fixed in 0.13.3-1

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2020-7695 Red Hat Product Security

    uvicorn: crafted input leads to HTTP response splitting

Full record on NVD

Fix

  1. Update Encode uvicorn to 0.11.7

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.15.3known since 2026-10-23
  • NVDCVSS 3.15.3read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-74read 2026-10-23
  • FIRST EPSSEPSS score1.4 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2020-07-29

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Published
2020-07-27
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-f97h-2pfx-f59f

Frequently asked questions

What is CVE-2020-7695?

Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.

Is CVE-2020-7695 actively exploited?

Active exploitation of CVE-2020-7695 has not been confirmed. Its EPSS score was 1.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-7695?

CVE-2020-7695 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.

Running Uvicorn? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record