CVE-2026-33752
Open Redirect and SSRF in curl_cffi Before
Publication date: 2026-04-06
Last updated on: 2026-04-09
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lexiforest | curl_cffi | to 0.15.0 (exc) |
| lexiforest | curl_cffi | 0.15.0 |
| lexiforest | curl_cffi | 0.15.0 |
| lexiforest | curl_cffi | 0.15.0 |
| lexiforest | curl_cffi | 0.15.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows attackers to access sensitive internal network services and cloud metadata endpoints by bypassing outbound filtering mechanisms. Such unauthorized access to internal resources can lead to exposure of confidential information.
Exposure of sensitive data through this Server-Side Request Forgery (SSRF) vulnerability could potentially result in non-compliance with data protection regulations such as GDPR and HIPAA, which require strict controls over access to personal and sensitive information.
Furthermore, the ability to impersonate TLS fingerprints to evade network controls may hinder detection and response efforts, increasing the risk of data breaches and regulatory violations.
Can you explain this vulnerability to me?
CVE-2026-33752 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Python package curl_cffi, which is a binding for curl. Prior to version 0.15.0, curl_cffi does not restrict requests to internal IP ranges and automatically follows HTTP redirects using the underlying libcurl library. This means an attacker can supply a URL that redirects requests to internal network services, such as cloud metadata endpoints, which are normally protected.
Additionally, curl_cffi has a TLS impersonation feature that can make these malicious requests appear as legitimate browser traffic, potentially bypassing network controls that filter outbound requests based on TLS fingerprints.
This vulnerability allows attackers to bypass restrictions limiting requests to external URLs by redirecting requests to internal services without validation at the Python layer.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to access sensitive internal network services and cloud metadata endpoints that should normally be inaccessible from outside the network.
By exploiting this SSRF vulnerability, attackers can bypass outbound filtering mechanisms and network controls, potentially gaining unauthorized access to confidential information stored in internal services.
The TLS impersonation feature can help attackers evade detection by making malicious requests appear as legitimate browser traffic.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual outbound requests made by curl_cffi that target internal IP ranges or cloud metadata endpoints, especially those that follow redirects automatically. Look for network traffic where curl_cffi is used to access internal IP addresses such as 127.0.0.1 or 169.254.0.0/16, or where TLS impersonation (e.g., impersonate="chrome") is employed, which may indicate attempts to bypass network controls.
To detect such activity, you can use network monitoring tools or commands to inspect outbound connections and HTTP redirects initiated by curl_cffi.
- Use packet capture tools like tcpdump or Wireshark to filter traffic from systems running curl_cffi and check for requests to internal IP ranges.
- Example tcpdump command to capture traffic to internal IP ranges: tcpdump -i any dst net 127.0.0.0/8 or dst net 169.254.0.0/16
- Check logs or use process monitoring to identify curl_cffi usage and inspect the URLs being requested.
- If possible, enable verbose or debug logging in curl_cffi to capture redirect chains and TLS impersonation usage.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation is to upgrade curl_cffi to version 0.15.0 or later, where this vulnerability is fixed by restricting requests to internal IP ranges and handling redirects securely.
Until the upgrade can be applied, consider implementing network-level controls to block outbound requests to internal IP ranges from systems running vulnerable versions of curl_cffi.
Additionally, monitor and restrict the use of TLS impersonation features in curl_cffi to prevent bypassing network filters.