Vulnerability in Haxx (CVE-2026-7168)
Summary
Vulnerability in Haxx (CVE-2026-7168). Risk of unauthorized operations or information disclosure. Exploitable via proxyA.
Original description
The description as published by the source.
Successfully using libcurl to do a transfer over a specific HTTP proxy
(proxyA) with Digest authentication and then changing the proxy host to
a second one (proxyB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Proxy-Authorization: header field meant for
proxyA, to proxyB.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-7168 has been found in Haxx.
Attackers can target a specific entry point like proxyA over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Haxx CVE-2026-7168" on the vendor's site.
CVE-2026-7168 (Haxx) — CWE-294 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: proxyA / proxyB
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.
A vulnerability (CWE-294) exists in Haxx. Attackers reach the vulnerable code path via proxyA without authentication.
Check the vendor advisory for the affected versions of Haxx. Attack surface: proxyA / proxyB.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Haxx' . 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 'Haxx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Haxxを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-7168 curl Fixed in: 8.20.0-r0
- BellSoft Alpaquita BELL-CVE-2026-7168 curl Fixed in: 8.20.0-r0
- Debian DEBIAN-CVE-2026-7168 curl
- Ubuntu UBUNTU-CVE-2026-7168 curl
References
- exploit hackerone.com
- patch curl.se
- patch curl.se
- patch openwall.com
- web nvd.nist.gov
- web github.com