CVE-2026-55960: Un-negotiated Raw Public Key (RFC 7250) accepted in place of X.509, bypassing chain validation
Un-negotiated Raw Public Key (RFC 7250) accepted in place of an X.509 certificate, bypassing chain validation. A raw public key has no chain, so ParseCertRelative() accepts it without performing any trust verification; it must therefore only be accepted when RPK was actually negotiated for that peer. The check now defaults the expected type to X.509 (per RFC 7250/8446) when no type was negotiated, comparing against the received server certificate type on the client and the selected client certificate type on the server, and rejects any mismatch, including an un-negotiated raw public key, with UNSUPPORTEDCERTIFICATE. Only affects builds with Raw Public Key support (HAVERPK) enabled - disabled by default in a standalone build, but included in --enable-all.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-55960?
The severity of CVE-2026-55960 is high, with a CVSS score of 8.2.
How does CVE-2026-55960 affect system security?
CVE-2026-55960 allows an un-negotiated raw public key to bypass chain validation, potentially leading to unauthorized access.
What software is affected by CVE-2026-55960?
CVE-2026-55960 affects OpenSSL and wolfSSL implementations.
How do I fix CVE-2026-55960?
To fix CVE-2026-55960, ensure that raw public key negotiation is properly configured and enabled.
When was CVE-2026-55960 published?
CVE-2026-55960 was published on June 25, 2026.