CVE-2026-55960
TLS accepts un-negotiated raw public key, bypassing cert chain validation.
Is CVE-2026-55960 being exploited?
Not confirmed. CVE-2026-55960 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-55960?
CVE-2026-55960 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55960?
Yes. A fix has been recorded for CVE-2026-55960. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55960 affect?
CVE-2026-55960 affects TLS libraries implementing RFC 7250 Raw Public Key with HAVE_RPK enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55960?
Apply patch when available; disable RPK if not required
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Impersonation/MITM via un-negotiated Raw Public Key when RPK is enabled; trust checks can be bypassed.
Patch when possible
- affected>= 5.6.4 and <= 5.9.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.