CVE-2026-11933
Description
A use-after-free in MongoDB's BSON-to-JS array conversion allows authenticated users to leak memory or crash the server.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A use-after-free in MongoDB's BSON-to-JS array conversion allows authenticated users to leak memory or crash the server.
Vulnerability
The vulnerability resides in the bsonObjToArray function within MongoDB's MozJS BSON binding layer. Unlike its sibling bsonGetImmutable, which ensures the BSON object is owned before creating JavaScript wrappers, bsonObjToArray does not apply the same ownership check. This inconsistency can lead to a use-after-free condition when operating on sub-document wrappers. Affected versions include MongoDB 8.0.27. [1]
Exploitation
An attacker must be an authenticated user with read privileges and the ability to execute server-side JavaScript, for example via the $where or $function operators. By crafting a query that triggers the conversion of a BSON sub-document to a JavaScript array, the attacker can cause the server to access memory that has already been freed. The exact steps involve sending a query that exploits the missing ownership check in bsonObjToArray. [1]
Impact
Successful exploitation can result in disclosure of sensitive information from the mongod process memory or a denial of service through a server crash. The attacker gains no direct code execution but can leak data or disrupt service availability. [1]
Mitigation
The issue is fixed in MongoDB 8.0.27, the version where it was reported. Users should upgrade to a patched version. No workarounds are mentioned in the available reference. [1]
AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.