Certificate revocation bypass via missing OCSP response
Published May 13, 2026 · Updated May 13, 2026
Improper certificate validation in curl 8.17.0 through 8.19.0 allows remote attackers to bypass OCSP stapling checks. The ossl_apple_verify function converts the TLS library's no-response result to an empty buffer, then accepts successful SecTrust verification. The flaw requires an OpenSSL-based backend, Apple SecTrust, and certificate-status verification on an Apple platform, allowing a revoked certificate without a stapled response to be trusted.
Summary
What happened
Improper certificate validation in curl 8.17.0 through 8.19.0 allows remote attackers to bypass OCSP stapling checks. The ossl_apple_verify function converts the TLS library's no-response result to an empty buffer, then accepts successful SecTrust verification. The flaw requires an OpenSSL-based backend, Apple SecTrust, and certificate-status verification on an Apple platform, allowing a revoked certificate without a stapled response to be trusted.
The record
- CVE
- CVE-2026-7009
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 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=8.17.0 <=8.17.0
- Affected versionversion=8.18.0 <=8.18.0
- Affected versionversion=8.19.0 <=8.19.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.
Weakness, pattern, technique
Public exploit references
- HackerOne report 3694390proof 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