PROXYGEN · CVE-2026-121737 · Runtime
NO FIX YET · SEE WHAT TO DO
A remote, unauthenticated HTTP/1.1 client can pipeline a second request and stop reading, causing proxygen's session to free that stream and then use it. This can crash the server and may allow memory corruption with further impact.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any service built on proxygen that accepts HTTP/1.1 connections from untrusted clients is exposed, since no authentication is needed. Systems that do not use proxygen, or that sit behind a proxy that fully handles HTTP/1.1 parsing, are less exposed; the sources do not say which deployments are safe.
Not affected if not-using-proxygen
Who cares c++, http-server, proxygen, self-hosted
v2026.11.09.00.v2026.11.09.00 or laterWhen a remote, unauthenticated HTTP/1.1 client pipelined the start of a second request and then stopped reading, proxygen's coroutine-based HTTP session could free that pipelined stream while resetting the connection's streams on the resulting write timeout, then go on to use it. This can crash the server, leading to denial of service, and may allow memory corruption with further impact. This issue affects proxygen versions prior to v2026.11.09.00.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.