Skip to main content
Vulnerability Database/CVE-2026-91095

CVE-2026-91095: Proxygen Use-After-Free Vulnerability

CVE-2026-91095 is a use-after-free vulnerability in Proxygen that affects WebTransport stream handling, potentially allowing access to freed memory. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-91095 Overview

CVE-2026-91095 is a use-after-free vulnerability [CWE-416] in Facebook's proxygen HTTP libraries. The flaw affects versions from v2024.10.28.00 until v2026.09.28.00. The HTTPTransaction::onWebTransportUniStream and HTTPTransaction::onWebTransportBidiStream APIs could return stream handles that the stream handler had already freed. HQSession then installed those handles as transport read callbacks, leading to use of freed memory.

Critical Impact

Remote attackers can trigger memory access on freed stream handles in proxygen-based HTTP/3 and WebTransport services, resulting in availability loss without authentication.

Affected Products

  • Facebook proxygen versions v2024.10.28.00 through versions prior to v2026.09.28.00
  • Applications embedding proxygen's HQSession with WebTransport support
  • HTTP/3 services built on proxygen exposing bidirectional or unidirectional WebTransport streams

Discovery Timeline

  • 2026-09-28 - CVE-2026-91095 published to the National Vulnerability Database
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-91095

Vulnerability Analysis

The vulnerability exists in proxygen's WebTransport stream lifecycle management within HQSession.cpp. When a new WebTransport stream arrives, HQSession calls either HTTPTransaction::onWebTransportBidiStream or HTTPTransaction::onWebTransportUniStream to obtain a read handle. These calls invoke user-provided stream handlers synchronously. The handler may end the transaction, which frees the returned handle before HQSession installs it as the transport read callback.

Because HQSession did not verify handle validity or guard the transaction against destruction, subsequent calls to sock_->setReadCallback operated on freed memory. Any inbound data on the affected stream then dereferenced the dangling callback pointer.

Root Cause

The root cause is missing lifetime management between the transaction, the stream handler callback, and the read handle returned to HQSession. The code assumed the handle remained valid after the handler executed, but the handler can terminate the transaction and free associated resources during its own execution.

Attack Vector

A remote unauthenticated attacker opens a WebTransport bidirectional or unidirectional stream to a vulnerable proxygen-based server. If the server's stream handler ends the session or calls stopSending inline, the freed handle is installed as a read callback. Subsequent stream activity triggers use-after-free, typically causing a crash and denial of service.

cpp
     return;
   }
   connectStream->txn_.getWebTransport(); // lazy-init webTransportImpl_
+  // The handler runs below and can end the txn, freeing the handle.
+  HTTPTransaction::DestructorGuard dg(&connectStream->txn_);
+  WebTransportImpl::StreamReadHandle* readHandle = nullptr;
   if (sock_->isBidirectionalStream(streamID)) {
-    auto handle = connectStream->txn_.onWebTransportBidiStream(streamID);
-    sock_->setReadCallback(streamID, handle.readHandle);
+    readHandle =
+        connectStream->txn_.onWebTransportBidiStream(streamID).readHandle;
   } else {
-    auto* handle = connectStream->txn_.onWebTransportUniStream(streamID);
-    sock_->setReadCallback(streamID, handle);
+    readHandle = connectStream->txn_.onWebTransportUniStream(streamID);
+  }
+  // No handle means the handler ended the session; an unregistered one means
+  // it called stopSending.
+  if (readHandle && readHandle->readCallbackRegistered()) {
+    sock_->setReadCallback(streamID, readHandle);
   }
 }

Source: GitHub Proxygen Commit 479eb55. The patch introduces a DestructorGuard on the transaction, captures the read handle explicitly, and validates that a handle was returned and its callback is still registered before installing it.

Detection Methods for CVE-2026-91095

Indicators of Compromise

  • Unexpected crashes or restarts of proxygen-based HTTP/3 or WebTransport services correlated with inbound WebTransport stream activity
  • Address Sanitizer or heap-checker reports referencing HQSession::onNewStream and WebTransportImpl::StreamReadHandle
  • Anomalous WebTransport stream open followed immediately by session termination from the same client

Detection Strategies

  • Deploy debug builds with AddressSanitizer in staging to surface use-after-free traces on the setReadCallback code path
  • Monitor service telemetry for crash signatures in HQSession.cpp around WebTransport bidi and uni stream handlers
  • Inspect HTTP/3 access logs for high rates of short-lived WebTransport streams from single sources

Monitoring Recommendations

  • Alert on process crash loops for services linking proxygen versions in the vulnerable range
  • Track QUIC and HTTP/3 connection error rates, particularly stream reset and session close counts
  • Forward crash dumps and stack traces to a centralized data lake for correlation with network-side telemetry

How to Mitigate CVE-2026-91095

Immediate Actions Required

  • Upgrade proxygen to v2026.09.28.00 or later, which contains commit 479eb55
  • Rebuild and redeploy all downstream services statically or dynamically linked against vulnerable proxygen versions
  • Audit custom HTTPTransactionHandler implementations that terminate sessions or call stopSending inside WebTransport stream callbacks

Patch Information

The fix is available in the proxygen repository as commit 479eb55. Additional vendor context is published in the Facebook Security Advisory CVE-2026-91095. The patch adds an HTTPTransaction::DestructorGuard around the handler invocation and validates the read handle before installing it as the transport read callback.

Workarounds

  • If patching is not immediately possible, disable WebTransport support in the proxygen server configuration until the update is deployed
  • Restrict WebTransport endpoints behind authenticated reverse proxies to limit unauthenticated exposure
  • Implement rate limiting on HTTP/3 stream creation to reduce opportunities to trigger the freed-handle path
bash
# Verify installed proxygen version and update to the fixed release
git -C proxygen fetch --tags
git -C proxygen checkout v2026.09.28.00
cd proxygen && ./build.sh

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.