CVE-2026-87866: wolfSSL public-key pinning bypass
- Is it exploited?
Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.
- How likely is exploitation in the next 30 days?
- 0.2%
EPSS score, percentile 10.9 of all scored records. A probability estimated by FIRST, not a report of exploitation.
CISA's SSVC assessment in the CVE record lists exploitation as poc.
- How severe?
- 9.1 Critical
CVSS v3.1 base score, from CISA's enrichment of the record
- What should I do?
CISA has set no required action, because the vulnerability is not in KEV.
The CVE record links no vendor advisory, patch or mitigation.
- Which versions are affected?
Affected
- 8.22.0 through 8.22.0
- 8.21.0 through 8.21.0
- 8.20.0 through 8.20.0
- 8.19.0 through 8.19.0
- 8.18.0 through 8.18.0
- 8.17.0 through 8.17.0
and 6 more in the table below
Source: CISA KEV 2026.10.29, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.
What to do
Advisories and patches
The CVE record links no vendor advisory, patch or mitigation.
This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.
Affected products and versions
As listed in the CVE record.
| Status | Versions |
|---|---|
| Affected | 8.22.0 through 8.22.0 |
| Affected | 8.21.0 through 8.21.0 |
| Affected | 8.20.0 through 8.20.0 |
| Affected | 8.19.0 through 8.19.0 |
| Affected | 8.18.0 through 8.18.0 |
| Affected | 8.17.0 through 8.17.0 |
| Affected | 8.16.0 through 8.16.0 |
| Affected | 8.15.0 through 8.15.0 |
| Affected | 8.14.1 through 8.14.1 |
| Affected | 8.14.0 through 8.14.0 |
| Affected | 8.13.0 through 8.13.0 |
| Affected | 8.12.1 through 8.12.1 |
Versions not listed are: unaffected.
And 88 more version entries in the CVE record.
Source: CVE List, as of . About the data.
About this vulnerability
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field - extracts and matches a different embedded key, incorrectly authorizing the pinned public key.
Summary: CVE record, as of .
- CISA has not added CVE-2026-87866 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
- The CVE record was published on 20 Oct 2026.
- The CVE record carries a CVSS v3.1 base score of 9.1 (Critical), taken from CISA's enrichment of the record.
- FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.2% (percentile 10.9), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
- CISA's SSVC assessment in the CVE record: exploitation poc, automatable yes, technical impact total.
Source: CISA KEV 2026.10.29, as of ; CVE List, as of ; FIRST EPSS, as of . About the data.
Description
wolfSSL public-key pinning bypass
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field - extracts and matches a different embedded key, incorrectly authorizing the pinned public key.
Source: CVE List, as of . About the data.
Weakness
CWE-295
- CWE-295: Improper Certificate Validation
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.
Timeline
| Date | Event |
|---|---|
| CVE record published | |
| CVE record last updated |