CVE-2026-55960: Un-negotiated Raw Public Key (RFC 7250) accepted in place of an X.509 certificate, bypassing chain validation
CVE-2026-55960 is a high-severity flaw (CVSS 7.5) affecting wolfssl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 86%) |
| CISA exploited list | No |
| Weakness | CWE-295 |
| Published | 2026-06-25 |
| Last modified | 2026-06-26 |
Last updated 2026-06-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-55960?
wolfssl: upgrade to 5.9.2. Exact commands for each OS are on this page.
Is CVE-2026-55960 being exploited?
CVE-2026-55960 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-55960 affect?
CVE-2026-55960 affects wolfssl. Severity is high (CVSS 7.5). 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 onl
How urgent is CVE-2026-55960?
Priority 35/100. High severity; Remotely exploitable, no login, no user action
Software pages
Related CVEs
- CVE-2026-55967 HIGH 7.5 UPGRADE AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly
- CVE-2026-5263 MEDIUM 6.5 UPGRADE URI nameConstraints from constrained intermediate CAs are parsed but not enforced during certificate chain ver
- CVE-2026-7532 HIGH 7.5 UPGRADE iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not defined
- CVE-2026-6678 MEDIUM 5.3 UPGRADE Integer underflow in wc_PKCS7_DecryptOri when handling crafted Other Recipient Info, leading to incorrect leng
- CVE-2026-6679 HIGH 7.5 UPGRADE A heap buffer overflow could occur in the DTLS 1.3 ACK serialization path before the connecting peer is authen