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-84895 Overview
CVE-2026-84895 is a use-after-free vulnerability in Meta's proxygen HTTP library. The flaw resides in QuicWtSession::closeSession, which accesses member fields after invoking the base QuicWtSessionBase::closeSession method. The base method notifies the session handler, and that handler may release the last reference to the session object, causing its destruction. Any subsequent member access reads freed memory.
The vulnerability affects proxygen builds from v2026.04.06.00 up to (but not including) v2026.09.28.00. Proxygen provides the HTTP/QUIC stack behind large-scale Meta services and third-party consumers using WebTransport over QUIC.
Critical Impact
A remote peer that can trigger session teardown during a WebTransport close sequence may cause memory corruption or process crash in proxygen-based servers and clients.
Affected Products
- Meta proxygen from v2026.04.06.00 through versions prior to v2026.09.28.00
- Applications embedding proxygen's WebTransport-over-QUIC session layer (QuicWtSession)
- Downstream services that link proxygen builds within the affected window
Discovery Timeline
- 2026-09-28 - CVE-2026-84895 published to the National Vulnerability Database (NVD)
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-84895
Vulnerability Analysis
The defect is a classic use-after-free ([CWE-416]) in C++ code that manages object lifetime across a callback boundary. QuicWtSession::closeSession first calls into QuicWtSessionBase::closeSession. The base implementation notifies the session handler, which is free to react by clearing the last owning reference to the derived QuicWtSession instance. Control then returns to the derived method, which continues to dereference this and touch member fields on an object that no longer exists.
Exploitation depends on triggering a code path where the handler destroys the session synchronously during notification. WebTransport sessions expose that path because peers can initiate close sequences and streams can be torn down while handlers unwind. Memory reuse of the freed session allocation can turn the dangling access into type confusion or arbitrary write primitives depending on the allocator state.
Root Cause
The derived method fails to guard the lifetime of this before delegating to the base class. There is no DestructorGuard or equivalent smart-pointer retention around the notification, so any handler decision to release the session immediately invalidates the remainder of closeSession.
Attack Vector
A remote WebTransport peer that can drive a session into close during an active handler callback can cause the after-free access. The attack does not require authentication when the WebTransport endpoint is exposed to untrusted clients. Consequences range from process crash (denial of service) to memory corruption suitable for further exploitation.
// Fix from proxygen HQSession.cpp — protect the session/txn across
// handler callbacks that may free the last reference.
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 — facebook/proxygen
Detection Methods for CVE-2026-84895
Indicators of Compromise
- Unexpected SIGSEGV or SIGABRT terminations in proxygen-based server processes correlated with WebTransport session closes
- AddressSanitizer or heap-checker reports flagging heap-use-after-free inside QuicWtSession::closeSession frames
- Core dumps whose backtraces include QuicWtSessionBase::closeSession followed by member access in the derived class
Detection Strategies
- Inventory linked proxygen versions across services; flag any build in the range v2026.04.06.00 through < v2026.09.28.00
- Enable ASan or HWASan in staging fuzzing runs that exercise WebTransport close and stream teardown
- Add crash telemetry rules that correlate rapid session churn from a single QUIC peer with process restarts
Monitoring Recommendations
- Forward crash reports and stack traces to a centralized SIEM or data lake for pattern analysis
- Track anomalous rates of QUIC connection resets and WebTransport CLOSE_SESSION capsules per source
- Alert on repeated worker restarts for HTTP/QUIC frontends serving WebTransport traffic
How to Mitigate CVE-2026-84895
Immediate Actions Required
- Upgrade proxygen to v2026.09.28.00 or later, which contains commit 479eb55
- Rebuild and redeploy every downstream binary that statically links or vendors affected proxygen sources
- If patching is delayed, disable WebTransport endpoints or restrict them to trusted clients
Patch Information
The fix is included in the proxygen re-sync commit 479eb5574195764e80e6cedebef669f6baa85083, which introduces a HTTPTransaction::DestructorGuard around handler callbacks and refactors QuicWtSession::closeSession so member access no longer follows a base call that can destroy the object. Refer to the GitHub commit for proxygen and the Facebook Security Advisory CVE-2026-84895 for the authoritative fix details.
Workarounds
- Terminate WebTransport-over-QUIC at an unaffected reverse proxy while backend proxygen builds are updated
- Apply network ACLs to limit which peers can open WebTransport sessions to proxygen endpoints
- Enable process supervisors with rate-limited restarts to contain repeated crash-driven denial of service
# Verify the running proxygen build is at or above the fixed release
git -C proxygen describe --tags
# Expected: v2026.09.28.00 or newer
# Rebuild after updating the submodule / dependency pin
git -C proxygen fetch --tags
git -C proxygen checkout v2026.09.28.00
cmake --build build --target proxygen -- -j
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

