CVE-2026-55964

MEDIUMNVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

Chain intermediate CA:TRUE without keyCertSign accepted as a signing CA. Intermediate CA certificates are required to have the keyCertSign key usage when a Key Usage extension is present, but chain-supplied temporary CAs (WOLFSSL_TEMP_CA) added while building a certificate path were previously exempted from this check, so an intermediate asserting CA:TRUE but lacking keyCertSign was accepted as a signing CA. The check now applies to chain-supplied temporary CAs as well; only operator-loaded root certificates (WOLFSSL_USER_CA) and self-signed roots remain exempt. Per RFC 5280 an absent Key Usage extension implies all usages, so the requirement is enforced only when the extension is actually present (extKeyUsageSet). Affects the OpenSSL-compatibility certificate-path-building path (X509_verify_cert / X509_STORE, OPENSSL_EXTRA/OPENSSL_ALL), where untrusted chain intermediates are added as temporary CAs; native (non-OpenSSL-compat) certificate verification does not create temporary CAs and is unaffected. Within those builds, the check applies unless ALLOW_INVALID_CERTSIGN is defined.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
2.0%
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 26× in last 7d / 44× 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-06 21:01 UTCEG score recompute
  2. 2026-07-06 21:01 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 22:41 UTCEG score recompute
  8. 2026-07-05 22:41 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 00:26 UTCEG score recompute
  12. 2026-07-05 00:26 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 02:08 UTCEG score recompute
  16. 2026-07-04 02:08 UTCGHSA enrichment
  17. 2026-07-03 03:49 UTCEG score recompute
  18. 2026-07-03 03:49 UTCGHSA enrichment
  19. 2026-07-02 05:20 UTCEG score recompute
  20. 2026-07-02 05:20 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-07-01 07:04 UTCEG score recompute
  23. 2026-07-01 07:04 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 08:49 UTCEG score recompute
Show 19 more
  1. 2026-06-30 08:49 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 10:34 UTCEG score recompute
  5. 2026-06-29 10:33 UTCGHSA enrichment
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 12:17 UTCEG score recompute
  8. 2026-06-28 12:17 UTCGHSA enrichment
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-27 14:00 UTCEG score recompute 1.00
  12. 2026-06-27 14:00 UTCGHSA enrichment
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 5.3
  15. 2026-06-26 15:45 UTCEG score recompute 6.30
  16. 2026-06-26 15:45 UTCGHSA enrichment
  17. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3
  18. 2026-06-25 21:46 UTCEG score recompute
  19. 2026-06-25 21:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-55964?
CVE-2026-55964 is a medium vulnerability published on June 25, 2026. Chain intermediate CA:TRUE without keyCertSign accepted as a signing CA. Intermediate CA certificates are required to have the keyCertSign key usage when a Key Usage extension is present, but chain-supplied temporary CAs (WOLFSSLTEMPCA) added while building a certificate path were previously…
When was CVE-2026-55964 disclosed?
CVE-2026-55964 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-55964 actively exploited?
CVE-2026-55964 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55964?
CVE-2026-55964 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-55964?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55964, 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-55964

Explore →

Is Your Infrastructure Affected by CVE-2026-55964?

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