# CVE-2026-119332: Ladybird: FinalizationRegistry::cleanup() heap use-after-free via reentrant unregister()


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-6cmv-xmff-qjph

## What is CVE-2026-119332?

CVE-2026-119332 is a high-severity vulnerability in LadybirdBrowser ladybird, published on 30 Oct 2026. 

### Official description

Ladybird is a truly independent web browser. Prior to 209579c96473c75bd5eba9701fcadb841a045964, FinalizationRegistry::cleanup() in Libraries/LibJS/Runtime/FinalizationRegistry.cpp removed a dead record from m_records, retained an iterator to the next FinalizationRecord, and then invoked attacker-controlled JavaScript through the cleanup callback. If that callback called unregister() for the next record, remove_by_token() freed the node referenced by the retained iterator, and the next cleanup iteration read its target and held_value fields after free. This reliably crashes instrumented WebContent builds and creates a memory-corruption primitive in production builds. This vulnerability is fixed by commit 209579c96473c75bd5eba9701fcadb841a045964.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-119332 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119332 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119332 is a high-severity vulnerability in LadybirdBrowser ladybird, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119332 exists.

Affected product: LadybirdBrowser ladybird. 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-119332/ (Markdown: https://insights.sbomify.com/CVE-2026-119332/index.md)
```

## Sources

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

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