Vulnerability Description
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 UNSUPPORTED_CERTIFICATE. Only affects builds with Raw Public Key support (HAVE_RPK) enabled - disabled by default in a standalone build, but included in --enable-all.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Wolfssl | Wolfssl | >= 5.6.4, < 5.9.2 |
Related Weaknesses (CWE)
References
- https://github.com/wolfSSL/wolfssl/pull/10702Issue TrackingPatch
- https://www.wolfssl.com/docs/security-vulnerabilities/Vendor Advisory
FAQ
What is CVE-2026-55960?
CVE-2026-55960 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 t...
How severe is CVE-2026-55960?
CVE-2026-55960 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-55960?
Check the references section above for vendor advisories and patch information. Affected products include: Wolfssl Wolfssl.