How severe is CVE-2025-10097?

No CVSS score has been assigned to CVE-2025-10097 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-10097?

CVE-2025-10097 affects the following packages: simstudio (npm). Ecosystems affected: npm.

How do I fix CVE-2025-10097?

The records we use list no patched version of simstudio for CVE-2025-10097. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2025-10097 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simstudio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-10097 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2025-10097 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-10097 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-10097?

CVE-2025-10097 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-10097?

CVE-2025-10097 is classified as CWE-74 (CWE-74), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-10097 published, and has it been updated?

CVE-2025-10097 was published on September 8, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-10097 — simstudio

Fix: simstudioai/sim#1149

CVE-2025-10097 is a CWE-74 vulnerability in simstudio. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

SimStudioAI sim route.ts code injection

Also known asGHSA-g4c9-f287-64xg

Published

Sep 8, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10097.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

simstudionpm

27downloads / week

Description

A vulnerability was identified in SimStudioAI sim up to 1.0.0. This impacts an unknown function of the file apps/sim/app/api/function/execute/route.ts. The manipulation of the argument code leads to code injection. The attack is possible to be carried out remotely.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`simstudio`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

simsim

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simstudio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of simstudio for CVE-2025-10097. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-10097 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works