🛡️ CVE-2026-9079 — curl
Description
libcurl had a flaw that when instructed to clear proxy authentication
credentials which made it not do so, leaving the old credentials around to get
used for subsequent transfers that should not know nor use them.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
Weakness class
CVE-2026-9079 is classified as CWE-522: Insufficiently Protected Credentials. Credentials are stored or transmitted with protection too weak for what they unlock.
Affected software
CVE-2026-9079 is recorded against 1 package.
- curl (from 8.8.0 up to 8.21.0)
Timeline and source
Published on 3 July 2026 and last revised on 7 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from NVD.
References
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| curl | 8.8.0 | 8.21.0 |
References
Similar Threats
- Unknown ALPINE-CVE-2022-32221
- Unknown ALPINE-CVE-2022-35260
- Unknown ALPINE-CVE-2022-35252
- Unknown ALPINE-CVE-2022-32206
- Unknown ALPINE-CVE-2022-32205
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Exploit Protection
Are you running curl?
CVE-2026-9079 carries CVSS 9.8 Critical rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.
Check My Site For CVE-2026-9079 →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.