Client certificate substitution via ambiguous name lookup
Published Aug 5, 2021 · Updated May 28, 2026
Certificate-selection confusion in curl 7.33.0 through 7.77.0 allows local users to make libcurl send an attacker-chosen client certificate. With the macOS Secure Transport backend, CURLOPT_SSLCERT treats a matching file in the working directory as the certificate before checking the keychain name. The attack requires a shared writable current directory and a predictable certificate name; a planted file then replaces the intended identity in the TLS handshake.
Summary
What happened
Certificate-selection confusion in curl 7.33.0 through 7.77.0 allows local users to make libcurl send an attacker-chosen client certificate. With the macOS Secure Transport backend, CURLOPT_SSLCERT treats a matching file in the working directory as the certificate before checking the keychain name. The attack requires a shared writable current directory and a predictable certificate name; a planted file then replaces the intended identity in the TLS handshake.
The record
- CVE
- CVE-2021-22926
- Published
- Aug 5, 2021
- Updated
- May 28, 2026
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-295, T1036
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 5, 2021CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=curll 7.33.0 to and include 7.77.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- HackerOne report 1234760 proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo