CVE-2025-10619: @sequa ai/sequa mcp @sequa-ai/sequa-mcp Has Command Injection Vulnerability Vulnerability
MODERATECVE-2025-10619 is a MODERATE (CVSS 6.3) @sequa-ai/sequa-mcp has command injection vulnerability vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting @sequa ai/sequa mcp libraries in the npm ecosystem. The issue involves @sequa-ai/sequa-mcp has command injection vulnerability. Remediation is available by upgrading affected packages to version 1.0.14.
CVE-2025-10619 at a Glance
Security Impact
CVSS: 6.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).
How to Fix CVE-2025-10619
To remediate this vulnerability, upgrade all affected @sequa ai/sequa mcp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @sequa-ai/sequa-mcp@1.0.14
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @sequa-ai/sequa-mcp
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-10619, inspect your project dependencies using npm:
npm ls @sequa-ai/sequa-mcp
Analyze the terminal output to locate any version of @sequa ai/sequa mcp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.14), your application is affected.
Note: The npm ls @sequa-ai/sequa-mcp command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In @sequa ai/sequa mcp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-10619 Affected @sequa ai/sequa mcp Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@sequa-ai/sequa-mcp
|
npm |
< 1.0.14
|
1.0.14
|
References
Frequently Asked Questions
What is CVE-2025-10619?
Which @sequa ai/sequa mcp versions are affected?
What version fixes CVE-2025-10619?
Is @sequa-ai/sequa-mcp affected?
What is the CVSS score of CVE-2025-10619?
What CWE is associated with CVE-2025-10619?
How can I check npm dependencies for CVE-2025-10619?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9pw5-wx67-q964",
"modified" : "2025-09-25T21:33:10Z",
"published" : "2025-09-17T21:30:43Z",
"aliases" : [ "CVE-2025-10619" ],
"summary" : "@sequa-ai/sequa-mcp has Command Injection vulnerability",
"details" : "A vulnerability was detected in sequa-ai sequa-mcp up to 1.0.13. This affects the function redirectToAuthorization of the file src/helpers/node-oauth-client-provider.ts of the component OAuth Server Discovery. Performing manipulation results in os command injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. Upgrading to version 1.0.14 is able to mitigate this issue. The patch is named e569815854166db5f71c2e722408f8957fb9e804. It is recommended to upgrade the affected component. The vendor explains: \"We only promote that mcp server with our own URLs that have a valid response, but yes if someone would use it with a non sequa url, this is a valid attack vector. We have released a new version (1.0.14) that fixes this and validates that only URLs can be opened.\"",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@sequa-ai/sequa-mcp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.0.14"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-10619"
}, {
"type" : "WEB",
"url" : "https://github.com/sequa-ai/sequa-mcp/commit/e569815854166db5f71c2e722408f8957fb9e804"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-9pw5-wx67-q964"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sequa-ai/sequa-mcp"
}, {
"type" : "WEB",
"url" : "https://www.npmjs.com/package/%40sequa-ai/sequa-mcp/v/1.0.14"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-77" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2025-09-18T19:54:57Z",
"nvd_published_at" : "2025-09-17T21:15:37Z"
}
}