CVE-2026-55960

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.5
EG Score
7.5(high)
EPSS
4.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_pr.
generic Patch Available

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
github_pr

Various fixes

Fix merged in wolfSSL/wolfssl PR #10702 on 2026-06-17 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/10702

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 40× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 02:33 UTCEG score recompute
  2. 2026-07-07 02:33 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:10 UTCEG score recompute
  6. 2026-07-06 15:10 UTCGHSA enrichment
  7. 2026-07-06 03:46 UTCEG score recompute
  8. 2026-07-06 03:46 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 16:22 UTCEG score recompute
  12. 2026-07-05 16:21 UTCGHSA enrichment
  13. 2026-07-05 04:58 UTCEG score recompute
  14. 2026-07-05 04:58 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 17:30 UTCEG score recompute
  18. 2026-07-04 17:30 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:07 UTCEG score recompute
  22. 2026-07-04 06:07 UTCGHSA enrichment
  23. 2026-07-03 18:43 UTCEG score recompute
  24. 2026-07-03 18:43 UTCGHSA enrichment
  25. 2026-07-03 07:21 UTCEG score recompute
Show 41 more
  1. 2026-07-03 07:21 UTCGHSA enrichment
  2. 2026-07-02 19:57 UTCEG score recompute
  3. 2026-07-02 19:57 UTCGHSA enrichment
  4. 2026-07-02 08:35 UTCEG score recompute
  5. 2026-07-02 08:34 UTCGHSA enrichment
  6. 2026-07-01 21:10 UTCEG score recompute
  7. 2026-07-01 21:10 UTCGHSA enrichment
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-07-01 09:46 UTCEG score recompute
  10. 2026-07-01 09:45 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 22:20 UTCEG score recompute
  13. 2026-06-30 22:20 UTCGHSA enrichment
  14. 2026-06-30 10:57 UTCEG score recompute
  15. 2026-06-30 10:57 UTCGHSA enrichment
  16. 2026-06-29 23:26 UTCEG score recompute
  17. 2026-06-29 23:26 UTCGHSA enrichment
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 12:04 UTCEG score recompute
  21. 2026-06-29 12:04 UTCGHSA enrichment
  22. 2026-06-29 00:40 UTCEG score recompute
  23. 2026-06-29 00:40 UTCGHSA enrichment
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 13:16 UTCEG score recompute
  26. 2026-06-28 13:16 UTCGHSA enrichment
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 01:53 UTCEG score recompute
  30. 2026-06-28 01:53 UTCGHSA enrichment
  31. 2026-06-27 14:30 UTCEG score recompute
  32. 2026-06-27 14:30 UTCGHSA enrichment
  33. 2026-06-27 03:08 UTCEPSS rescore
  34. 2026-06-27 03:07 UTCEG score recompute 0.70
  35. 2026-06-27 03:07 UTCGHSA enrichment
  36. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 7.5
  37. 2026-06-26 15:45 UTCEG score recompute 8.20
  38. 2026-06-26 15:45 UTCGHSA enrichment
  39. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
  40. 2026-06-25 21:46 UTCEG score recompute
  41. 2026-06-25 21:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-55960?
CVE-2026-55960 is a high vulnerability published on June 25, 2026. 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…
When was CVE-2026-55960 disclosed?
CVE-2026-55960 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55960 actively exploited?
CVE-2026-55960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55960?
CVE-2026-55960 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55960, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55960

Explore →

Is Your Infrastructure Affected by CVE-2026-55960?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.