How severe is CVE-2025-9654?

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

Which packages are affected by CVE-2025-9654?

CVE-2025-9654 affects the following packages: @aiondadotcom/mcp-ssh (npm). Ecosystems affected: npm.

How do I fix CVE-2025-9654?

Update @aiondadotcom/mcp-ssh to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9654 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2025-9654 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-9654 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-9654 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-9654?

CVE-2025-9654 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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-9654?

CVE-2025-9654 is classified as CWE-74 (CWE-74), CWE-77 (CWE-77). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2025-9654 was published on August 29, 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.

CVE-2025-9654: @aiondadotcom/mcp

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk-0.12%

Lower risk than most CVEs68th percentile — riskier than 68% 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

@aiondadotcom/mcp-sshnpm

450downloads / week

Description

A security flaw has been discovered in AiondaDotCom mcp-ssh up to 1.0.3. Affected by this issue is some unknown functionality of the file server-simple.mjs. Performing manipulation results in command injection. The attack can be initiated remotely. Upgrading to version 1.0.4 and 1.1.0 can resolve this issue. The patch is named cd2566a948b696501abfa6c6b03462cac5fb43d8. It is advisable to upgrade the affected component.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@aiondadotcom/mcp-ssh`	all versions	1.1.0`npm install @aiondadotcom/mcp-ssh@1.1.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aiondadotcom/mcp-ssh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @aiondadotcom/mcp-ssh to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9654 is resolved across your whole dependency graph.
Workarounds
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

A security flaw has been discovered in AiondaDotCom mcp-ssh up to 1.0.3. Affected by this issue is some unknown functionality of the file server-simple.mjs. Performing manipulation results in command injection. The attack can be initiated remotely. Upgrading to version 1.0.4 and 1.1.0 can resolve this issue. The patch is named cd2566a948b696501abfa6c6b03462cac5fb43d8. It is advisable to upgrade the affected component.

O3 Security · Impact-Aware SCA

Is CVE-2025-9654 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2025-9654 — @aiondadotcom/mcp-ssh