Quick answers
- Is CVE-2026-119235 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119235 being exploited in the wild.
- How severe is CVE-2026-119235?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Meta Proxygen before v2026.11.09.00.
- Is there a fix for CVE-2026-119235?
- Yes: fixed in proxygen v2026.11.09.00. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119235 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119235?
- Check whether you run Meta Proxygen at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: proxygen v2026.11.09.00
Technical details
The QPACK decoder fails to enforce size limits on string literals in encoder-stream instructions until after the entire literal has been received. An attacker can declare an arbitrarily large literal size and continuously send data, causing unbounded buffering for the connection lifetime. This bypasses normal size restrictions regardless of dynamic table capacity settings.
Affected products
- Meta proxygen before v2026.11.09.00
Timeline
- 2026-11-11: advisory