Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mvfst | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mvfst |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.114% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unbounded Memory Growth in mvfst QUIC Server from Excessive Handshake‑Level CRYPTO Data | |
| Weaknesses | CWE-399 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Facebook
Facebook mvfst |
|
| Vendors & Products |
Facebook
Facebook mvfst |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unbounded Memory Growth in mvfst QUIC Server from Excessive Handshake‑Level CRYPTO Data | |
| Weaknesses | CWE-399 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An mvfst QUIC server retained CRYPTO frame data received at an encryption level (Initial or Handshake) that the TLS handshake had already moved past. Because the transport treated this data as delivered, it did not count against the CRYPTO stream buffer limit. A remote, unauthenticated client could complete a handshake, withhold its acknowledgment of the server's HANDSHAKE_DONE frame so that Handshake keys stay in use, and keep sending Handshake-level CRYPTO data at increasing offsets, causing unbounded memory growth on the server and leading to denial of service. This issue affects mvfst versions prior to v2026.11.09.00. | |
| References |
|
No weakness.