cve.bz

CVE-2026-119237 facebook proxygen

no score yetEPSS 0.2%

facebook proxygen: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
Assigned by
Meta (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-119237 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119237?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119237?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119237 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-119237

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-119237](https://cve.bz/cve/badge/CVE-2026-119237.svg)](https://cve.bz/cve/CVE-2026-119237)

HTML:

<a href="https://cve.bz/cve/CVE-2026-119237"><img src="https://cve.bz/cve/badge/CVE-2026-119237.svg" alt="CVE-2026-119237"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Facebook proxygenfrom v0.0.0.0 before v2026.11.09.00

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON