Use-after-free in Wasm JS-BSON bridge lets read-only users read 24 KiB via $accumulator
- Exploited
- No known exploitation
- Fix
- Fixed in 9.0.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.0.7.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
MongoDB Server contains a use-after-free flaw in its server-side JavaScript execution component. A remote attacker who has logged in with only read privileges can submit a crafted command that runs JavaScript and receive a bounded amount of adjacent process memory in the result, which discloses information they are not authorized to access without affecting integrity or availability.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A memory-management flaw in the server-side JavaScript execution component of MongoDB Server can allow an authenticated user holding only read privileges to cause the server to access memory that has already been released. By submitting a specially crafted database command that runs user-supplied JavaScript, the user can cause a bounded amount of adjacent process memory to be returned in the command's result. This results in the user obtaining information they are not authorized to access. Integrity and availability are not affected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach17/20Affects MongoDB (a widely deployed server, runtime, framework or database)
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 9.0.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120819 (Use-after-free in Wasm JS-BSON bridge lets read-only users read 24 KiB via $accumulator), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-120819 (entry last updated 2026-11-10): Affected: - MongoDB MongoDB Server: from 9.0.0, fixed in 9.0.7 Fixed versions: 9.0.7. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-120819 is not listed as of cve.now's last read. This KEV status is for CVE-2026-120819 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://jira.mongodb.org/browse/SERVER-134893 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-120819 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-120819.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- MongoDB MongoDB Server
From 9.0.0 · fixed in 9.0.7
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120819
Is CVE-2026-120819 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-120819?
MongoDB Server: from 9.0.0 before 9.0.7.Source: cve.now feed data
How do I fix CVE-2026-120819?
Upgrade to a fixed version: 9.0.7.Source: cve.now feed data