# CVE-2026-84894: Use after free in moxygen

> A remote attacker can trigger a use-after-free in the Moxygen library by sending a specific data stream, potentially leading to code execution or crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-mqcv-532f-gp47

## What is CVE-2026-84894?

CVE-2026-84894 is a high-severity use after free vulnerability in Meta Platforms, Inc moxygen, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-84894?


## How do I fix CVE-2026-84894?

No fix has been published for CVE-2026-84894 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84894 being exploited?

There is no known exploitation of CVE-2026-84894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84894 and fix it if it is affected.

What it is: CVE-2026-84894 is a high-severity use after free vulnerability in Meta Platforms, Inc moxygen, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84894 in the wild and no public exploit code.

Affected product: Meta Platforms, Inc moxygen. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84894/ (Markdown: https://insights.sbomify.com/CVE-2026-84894/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84894
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84894
- OSV: https://osv.dev/vulnerability/CVE-2026-84894

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84894/
Summaries are generated and may contain mistakes; the official description above is the record.