SSRF (Server-Side Request Forgery) in curl-cffi (CVE-2026-33752)
Summary
SSRF in curl-cffi (CVE-2026-33752). Confidential information can be exposed externally. Exploitable via GET /test. Mitigation: upgrade to 0.15.0 or later.
Original description
The description as published by the source.
curl_cffi is the a Python binding for curl. Prior to 0.15.0, 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. This vulnerability is fixed in 0.15.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33752 has been found in curl-cffi.
Attackers can target a specific entry point like GET /test over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade curl-cffi to 0.15.0 or later.
If unsure, ask your IT team or search "curl-cffi CVE-2026-33752" on the vendor's site.
CVE-2026-33752 (curl-cffi) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /test
Patched: 0.15.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in curl-cffi. Attackers reach the vulnerable code path via GET /test without authentication.
Check the vendor advisory for the affected versions of curl-cffi. Attack surface: GET /test.
Severity: ?. Confidential information can be exposed externally.
Update to 0.15.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /test requests with malformed payloads or SQL meta-characters. Run grep -r 'curl-cffi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'curl-cffi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
curl-cffiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /test' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /testへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade curl-cffi to 0.15.0ステージング環境で 0.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /test on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com