Read the docs

Memory exhaustion in proxygen QPACK decoder on encoder stream

Priority LOW 22Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from CNA.

Summary

Facebook proxygen from v0.0.0.0 before v2026.11.09.00 enforces its QPACK size limit on string literals in encoder stream instructions only after the whole literal has arrived. A remote unauthenticated HTTP/3 peer can send an oversized literal on the QPACK encoder stream and keep sending data, so the decoder buffers it without bound for the life of the connection and exhausts memory. The flaw applies even when the QPACK dynamic table is disabled, and it causes denial of service.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

proxygen's QPACK decoder enforced its size limit on a string literal in an encoder-stream instruction only after the entire literal had been received. A remote, unauthenticated HTTP/3 peer could send an insert instruction on the QPACK encoder stream that declares an arbitrarily large literal and then keep sending data, causing the decoder to buffer it without bound for the lifetime of the connection and exhaust memory, leading to denial of service. The issue occurs regardless of the advertised QPACK dynamic table capacity, including when the dynamic table is disabled. This issue affects proxygen versions prior to v2026.11.09.00.

Why it matters now

EPSS 0.00177 7th percentileScored 2026-11-16
Fix Fixed proxygen (Facebook): v2026.11.09.00

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Metaproxygenv0.0.0.0 to before v2026.11.09.00v2026.11.09.00Patch availableCNA
  • proxygen VendorMeta Affected v0.0.0.0 to before v2026.11.09.00 Fixed in v2026.11.09.00 Patch available CNA

Remediation

Upgrade proxygen to v2026.11.09.00, the fixed version. The sources list no advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

  • Fix · CNA proxygen (Facebook) Fixed in v2026.11.09.00

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Facebook proxygen v2026.11.09.00

    4 records Highest priority Priority LOW 4 LOW

    Other records, highest priority first

    • TI-2026-89837 When a remote, unauthenticated HTTP/1.1 client pipelined the start of a second request…Priority LOW 22
    • TI-2026-89835 Proxygen HTTP/3 denial of service via QPACK blocked stream readsPriority LOW 22
    • TI-2026-89831 proxygen HTTP/3 codec memory and CPU exhaustion via slow large framesPriority LOW 22

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-119235
  2. 2026-11-11 Alias added: GHSA-cqq6-62v8-g6mg

References

  • TI-2025-34861 Unsafe deserialization in React Server Components enables RCE KEVCVSS 3.1CRITICAL 10.0
  • TI-2019-02633 Buffer overflow in WhatsApp VOIP stack allows remote code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2019-13416 Cross-site scripting and local file reading in WhatsApp Desktop KEVCVSS 3.1HIGH 8.2
  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2025-34857 Incomplete authorization in WhatsApp linked device sync messages KEVCVSS 3.1MEDIUM 5.4
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
See all 198 →

Sources