When curl is told to use the Certificate Status Request TLS extension, often referred to as *OCSP stapling*, to verify that the server certificate is valid, it fails to detect OCSP problems and instead wrongly consider the response as fine.
CVE-2026-7009
Score 5.3 from GitHub Security Advisory published 2026-05-13. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
May 13, 2026
Last Modified
May 14, 2026
Advisory Details (4)
Auto-updated Jun 17, 2026oss-security - [ADVISORY] curl: CVE-2026-7009: OCSP stapling bypass with Apple SecTrust
http://www.openwall.com/lists/oss-security/2026/04/29/12curl - OCSP stapling bypass with Apple SecTrust - CVE-2026-7009
https://curl.se/docs/CVE-2026-7009.htmlVendor Advisories for CVE-2026-7009(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | curl-main-8.20.0-2.hum1 | 2026-05-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 2 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.20.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.20.0-r0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 38× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 207 total refreshes for this CVE.
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:53 UTCOSV refresh
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-23 17:57 UTCEG score recompute
- 2026-08-23 17:57 UTCVendor advisory
- 2026-08-23 17:57 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 21:33 UTCEG score recompute
- 2026-08-20 21:33 UTCVendor advisory
- 2026-08-20 21:33 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:44 UTCEG score recompute
- 2026-08-17 10:44 UTCVendor advisory
- 2026-08-17 10:44 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:08 UTCEG score recompute
- 2026-08-16 04:08 UTCVendor advisory
- 2026-08-16 04:08 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:49 UTCEG score recompute
- 2026-08-15 01:49 UTCVendor advisory
- 2026-08-15 01:49 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 02:36 UTCEG score recompute
- 2026-08-14 02:36 UTCVendor advisory
- 2026-08-14 02:36 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:26 UTCEG score recompute
- 2026-08-12 23:26 UTCVendor advisory
- 2026-08-12 23:26 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 00:13 UTCEG score recompute
- 2026-08-12 00:13 UTCVendor advisory
- 2026-08-12 00:13 UTCGHSA enrichment
- 2026-08-11 00:59 UTCEG score recompute
- 2026-08-11 00:59 UTCVendor advisory
- 2026-08-11 00:59 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 01:12 UTCEG score recompute
- 2026-08-10 01:12 UTCVendor advisory
- 2026-08-10 01:12 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 01:58 UTCEG score recompute
- 2026-08-09 01:58 UTCVendor advisory
- 2026-08-09 01:58 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:12 UTCEG score recompute
- 2026-08-07 20:12 UTCVendor advisory
- 2026-08-07 20:12 UTCGHSA enrichment
- 2026-08-06 20:58 UTCEG score recompute
- 2026-08-06 20:58 UTCVendor advisory
- 2026-08-06 20:58 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 21:43 UTCEG score recompute
- 2026-08-05 21:43 UTCVendor advisory
- 2026-08-05 21:43 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 19:44 UTCEG score recompute
- 2026-08-03 19:44 UTCVendor advisory
- 2026-08-03 19:44 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 20:28 UTCVendor advisory
- 2026-08-02 20:28 UTCGHSA enrichment
- 2026-08-01 21:14 UTCEG score recompute
- 2026-08-01 21:14 UTCVendor advisory
- 2026-08-01 21:14 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-295
Frequently asked(5)
What is CVE-2026-7009?
When was CVE-2026-7009 disclosed?
Is CVE-2026-7009 actively exploited?
What is the CVSS score of CVE-2026-7009?
How do I remediate CVE-2026-7009?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7009
Is Your Infrastructure Affected by CVE-2026-7009?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.