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

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

CVE-2026-91096 is a use-after-free vulnerability in Proxygen that occurs when read callbacks are invoked after being freed. This post explains its technical details, affected versions, impact, and mitigation steps.

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-91096 Overview

CVE-2026-91096 is a use-after-free vulnerability [CWE-416] in Facebook's proxygen HTTP library. The flaw resides in WebTransportImpl::terminateSessionStreams (previously WebTransportImpl::destroy in releases before v2025.08.18.00). The function failed to unregister read callbacks for streams that were no longer open before destroying them. As a result, the transport layer could invoke a read callback that had already been freed, leading to memory corruption or process termination. The vulnerability affects proxygen from v2024.10.28.00 up to v2026.09.28.00 and is exploitable over the network without authentication or user interaction.

Critical Impact

A remote attacker can trigger invocation of freed callback memory by manipulating WebTransport stream lifecycle, potentially causing denial of service or memory disclosure in services that embed proxygen.

Affected Products

  • Facebook proxygen v2024.10.28.00 through v2026.09.28.00
  • Applications embedding vulnerable proxygen releases that expose WebTransport
  • HTTP/3 and QUIC-based services built on proxygen

Discovery Timeline

  • 2026-09-28 - CVE-2026-91096 published to NVD
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-91096

Vulnerability Analysis

The defect exists in proxygen's WebTransport session teardown path. When WebTransportImpl::terminateSessionStreams executes, it destroys stream state objects, including read handles associated with individual WebTransport streams. The prior implementation did not unregister the read callback from the underlying transport socket before releasing the handle. The transport retained a raw pointer to the callback and could dispatch a read event against the freed object.

The issue is a classic C++ ownership boundary failure. Callback registration created an implicit lifetime dependency between the socket and the handle, but destruction of the handle did not honor that dependency. Under concurrent I/O, freed memory could be re-invoked or reallocated between free and invocation.

Root Cause

The root cause is missing callback deregistration during stream teardown. The patch introduces a HTTPTransaction::DestructorGuard around handler execution and checks readHandle->readCallbackRegistered() before calling setReadCallback. This prevents attaching a stale handle to the socket and ensures the transport does not dispatch reads into freed memory.

Attack Vector

Exploitation requires a remote peer to establish a WebTransport session against a vulnerable proxygen-based endpoint and drive stream lifecycle transitions that trigger terminateSessionStreams. Because the vector is network reachable and requires no authentication, exposed HTTP/3 services are directly targetable.

cpp
// Patch excerpt: proxygen/lib/http/session/HQSession.cpp
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)) {
  readHandle =
      connectStream->txn_.onWebTransportBidiStream(streamID).readHandle;
} else {
  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 Commit 479eb55

Detection Methods for CVE-2026-91096

Indicators of Compromise

  • Unexpected crashes or SIGSEGV in proxygen-linked processes handling WebTransport sessions
  • AddressSanitizer or heap corruption reports referencing WebTransportImpl or StreamReadHandle
  • Abnormal QUIC/HTTP/3 stream churn from a single remote peer preceding a service restart

Detection Strategies

  • Inventory dependencies to identify services statically or dynamically linked against proxygen releases between v2024.10.28.00 and v2026.09.28.00
  • Enable ASan or heap protection in staging to surface use-after-free conditions during fuzzing of WebTransport endpoints
  • Correlate application crash telemetry with inbound HTTP/3 traffic patterns targeting WebTransport endpoints

Monitoring Recommendations

  • Alert on repeated worker process restarts on HTTP/3 frontends
  • Capture QUIC connection logs including stream open, reset, and close events for forensic reconstruction
  • Monitor for anomalous rates of stream termination or STOP_SENDING frames from individual peers

How to Mitigate CVE-2026-91096

Immediate Actions Required

  • Upgrade proxygen to v2026.09.28.00 or later and rebuild all dependent services
  • Rebuild and redeploy any downstream binaries that statically link the affected library versions
  • If patching is delayed, disable WebTransport support at the application configuration layer

Patch Information

The fix is available in commit 479eb55 of the facebook/proxygen repository. The patch adds a HTTPTransaction::DestructorGuard, defers read callback registration until after handler execution, and validates that the read handle is still registered before attaching it to the socket. Refer to the Facebook Security Advisory CVE-2026-91096 for vendor guidance.

Workarounds

  • Terminate HTTP/3 and WebTransport at an unaffected reverse proxy until the upstream is patched
  • Restrict WebTransport reachability using network ACLs to trusted client networks
  • Deploy process supervision with rate-limited restarts to reduce blast radius of triggered crashes
bash
# Verify installed proxygen version and rebuild against 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.