CVE-2026-55967
AES-GCM streaming APIs do not reject >64 GiB cumulative single messages, enabling counter wrap and keystream reuse
Description
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.
INFO
Published Date :
June 25, 2026, 4:53 p.m.
Last Modified :
June 25, 2026, 4:53 p.m.
Remotely Exploit :
No
Source :
wolfSSL
Affected Products
The following products are affected by CVE-2026-55967
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | LOW | 50d2cd11-d01a-48ed-9441-5bfce9d63b27 |
Solution
- Reject cumulative single message sizes exceeding the supported limit.
- Implement strict input validation for message sizes.
- Update cryptographic libraries to recommended versions.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-55967 vulnerability anywhere in the article.