CVE-2025-52385: Studio · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations should take immediate steps to mitigate this vulnerability. First, they should monitor Studio 3T vendor communications closely for official patches or updates addressing CVE-2025-52385 and apply them promptly once available. Until patches are released, organizations should restrict network access to Studio 3T instances, limiting exposure to trusted internal networks only and blocking external access via firewalls or network segmentation. Employing application-layer firewalls or intrusion detection/prevention systems to detect and block suspicious payloads targeting the child_process module can provide additional protection. Organizations should audit their environments to identify all instances of Studio 3T and assess exposure. Where feasible, consider temporarily discontinuing use of Studio 3T or replacing it with alternative MongoDB management tools that are not vulnerable. Implement strict input validation and monitoring on systems interacting with Studio 3T to detect anomalous behavior. Finally, ensure comprehensive backup and incident response plans are in place to quickly recover from potential exploitation.
Description
An issue in Studio 3T v.2025.1.0 and before allows a remote attacker to execute arbitrary code via a crafted payload to the child_process module