proxygen's HTTP/3 codec buffered an incomplete non-DATA frame, such as a control-stream frame, a frame of an unknown
Source GCVE Database
Not known to be exploited : upgrade to v2026.11.09.00 soon.
Data as of 11 Nov 2026, 19:48 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in v2026.11.09.00, 2026.11.09.00
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade proxygen to v2026.11.09.00; meta/proxygen to 2026.11.09.00.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Facebookproxygen | Affected
| Fixed in
|
GitHubmeta/proxygenpkg:github/meta/proxygenOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade proxygen to version v2026.11.09.00 or later, where this issue is fixed. No other mitigation is indicated.
Description
A vulnerability in proxygen's HTTP/3 codec allows a remote unauthenticated peer to cause unbounded memory growth and increased CPU usage by sending a very large incomplete non-DATA frame slowly. This can lead to denial of service. The issue affects proxygen versions prior to v2026.11.09.00.