Read the docs

Proxygen HTTP/3 denial of service via QPACK blocked stream reads

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

Proxygen's HTTP/3 session, from v0.0.0.0 before v2026.11.09.00, keeps reading a stream after its HEADERS block is paused while waiting for QPACK dynamic table entries. Because the unread data bypasses the session's ingress buffer limit and is re-scanned in full on every read, a remote, unauthenticated HTTP/3 peer can send a HEADERS block that references a dynamic table insert it never sends, followed by a continuous stream of data. This causes memory growth until the request times out and CPU usage that grows quadratically, leading to denial of service. The flaw applies when QPACK blocked streams are enabled, which is the default.

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

Description from the CNA

In proxygen's HTTP/3 session, when a HEADERS block referenced QPACK dynamic table entries that had not yet been received, header decoding for that stream was paused, but the session continued to read the stream from the QUIC transport. The unread data bypassed the session's ingress buffer limit, returned flow-control credit to the peer, and was re-scanned in full on every read. With QPACK blocked streams enabled (the default), a remote, unauthenticated HTTP/3 peer could send a HEADERS block that references a dynamic table insert it never sends, followed by a continuous stream of data, causing memory growth until the request timed out and CPU usage that grows quadratically, leading to denial of service. This issue affects proxygen versions prior to v2026.11.09.00.

Why it matters now

EPSS 0.00205 10th 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 Facebook proxygen to v2026.11.09.00 or later, which contains the 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-89833 Memory exhaustion in proxygen QPACK decoder on encoder streamPriority 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-119237
  2. 2026-11-11 Alias added: GHSA-gjx4-gr88-xhc9

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