CVE-2026-55967

HIGHNVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: LOW) 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.

AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly rejected by the streaming APIs, allowing counter wrap, keystream reuse, and consequent plaintext recovery.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.8%
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

20260616-aes-fixes

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

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

Vendor Advisories for CVE-2026-55967(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 81× 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-23 03:20 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 20:02 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 08:23 UTCGHSA enrichment
  11. 2026-07-15 20:43 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 09:03 UTCGHSA enrichment
  15. 2026-07-14 21:17 UTCGHSA enrichment
  16. 2026-07-14 09:38 UTCGHSA enrichment
  17. 2026-07-13 22:31 UTCEPSS rescore
  18. 2026-07-13 21:52 UTCGHSA enrichment
  19. 2026-07-13 10:13 UTCGHSA enrichment
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 22:31 UTCGHSA enrichment
  23. 2026-07-12 10:52 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 23:11 UTCGHSA enrichment
Show 56 more
  1. 2026-07-11 11:31 UTCGHSA enrichment
  2. 2026-07-10 23:50 UTCGHSA enrichment
  3. 2026-07-10 12:05 UTCGHSA enrichment
  4. 2026-07-10 00:26 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 12:37 UTCGHSA enrichment
  8. 2026-07-09 00:56 UTCGHSA enrichment
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 13:17 UTCGHSA enrichment
  12. 2026-07-08 01:37 UTCGHSA enrichment
  13. 2026-07-07 13:57 UTCGHSA enrichment
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 02:18 UTCGHSA enrichment
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 14:37 UTCGHSA enrichment
  20. 2026-07-06 02:54 UTCGHSA enrichment
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 15:14 UTCGHSA enrichment
  24. 2026-07-05 03:34 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 15:54 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-04 04:14 UTCGHSA enrichment
  31. 2026-07-03 16:35 UTCGHSA enrichment
  32. 2026-07-03 04:56 UTCGHSA enrichment
  33. 2026-07-02 17:17 UTCGHSA enrichment
  34. 2026-07-02 05:37 UTCGHSA enrichment
  35. 2026-07-01 17:57 UTCGHSA enrichment
  36. 2026-07-01 15:07 UTCEPSS rescore
  37. 2026-07-01 06:18 UTCGHSA enrichment
  38. 2026-06-30 23:22 UTCEPSS rescore
  39. 2026-06-30 18:38 UTCGHSA enrichment
  40. 2026-06-30 06:58 UTCGHSA enrichment
  41. 2026-06-29 19:15 UTCGHSA enrichment
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-29 14:06 UTCEPSS rescore
  44. 2026-06-29 07:35 UTCGHSA enrichment
  45. 2026-06-28 19:55 UTCEG score recompute▲ 5.50
  46. 2026-06-28 19:55 UTCGHSA enrichment
  47. 2026-06-28 14:07 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-28 04:56 UTCEPSS rescore
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  52. 2026-06-25 19:50 UTCEG score recompute▲ 2.00
  53. 2026-06-25 19:50 UTCGHSA enrichment
  54. 2026-06-25 19:49 UTCNVD updateCVSS v3 → 2 · CVSS v4 → 2
  55. 2026-06-25 18:46 UTCEG score recompute
  56. 2026-06-25 18:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-55967?
CVE-2026-55967 is a high vulnerability published on June 25, 2026. AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly rejected by the streaming APIs, allowing counter wrap, keystream reuse, and consequent plaintext recovery.
When was CVE-2026-55967 disclosed?
CVE-2026-55967 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-55967 actively exploited?
CVE-2026-55967 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55967?
CVE-2026-55967 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55967?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55967, 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-55967

Explore →

Is Your Infrastructure Affected by CVE-2026-55967?

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

Start Free Scan →Browse All CVEs