Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-52385: Remote Code Execution in Studio 3T child_process Module

Published Aug 13, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS1.2%70th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2025-52385CWE-94 · Improper Control of Generation of…

CVE-2025-52385 is a remote code execution vulnerability affecting Studio 3T version 2025.1.0 and earlier. According to the provided description, the issue allows a remote attacker to execute arbitrary code via a crafted payload targeting the child_process module. Based on the available information, the flaw appears to stem from improper handling of untrusted input passed to process-execution functionality, resulting in attacker-controlled code or command execution within the context of the affected application. Specific vulnerable functions, code paths, and trigger conditions are not provided in the available content.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to execute arbitrary code on the affected system in the security context of the Studio 3T application user. This can enable full compromise of the application environment, including execution of arbitrary commands, access to local data available to the user, installation of additional malware or persistence mechanisms, and potential lateral movement depending on host privileges and network position.

Mitigation

If you can’t patch tonight, do this now.

Until a patched version is deployed, limit exposure by restricting untrusted data from reaching functionality that may invoke the child_process module, reducing or eliminating remote access paths to the vulnerable feature, and running Studio 3T with the least privileges possible. Additional defensive measures include application allowlisting, endpoint detection and response, and network controls to reduce the likelihood and impact of exploitation. If the vulnerable functionality can be disabled or isolated, do so temporarily.

Remediation

Patch, then assume compromise.

Upgrade Studio 3T to a fixed version later than 2025.1.0 once a vendor patch or updated release is available. If an official security advisory or patched build has been issued, apply it promptly across all affected installations. Validate that any code paths invoking the child_process module no longer pass untrusted input into process execution APIs without strict validation, escaping, or safe argument handling.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2025-52385 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-52385 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-52385?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2025-52385.
Is there a patch for CVE-2025-52385?
Upgrade Studio 3T to a fixed version later than 2025.1.0 once a vendor patch or updated release is available. If an official security advisory or patched build has been issued, apply it promptly across all affected installations.
How severe is CVE-2025-52385?
CVE-2025-52385 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.2% (70th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.