What is CVE-2025-10619?

CVE-2025-10619 is a medium-severity command injection vulnerability in @sequa-ai/sequa-mcp (npm), affecting versions < 1.0.14. It is fixed in 1.0.14. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2025-10619?

CVE-2025-10619 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @sequa-ai/sequa-mcp are affected by CVE-2025-10619?

@sequa-ai/sequa-mcp (npm) versions < 1.0.14 is affected.

Is there a fix for CVE-2025-10619?

Yes. CVE-2025-10619 is fixed in 1.0.14. Upgrade to this version or later.

Is CVE-2025-10619 exploitable, and should I be worried?

Whether CVE-2025-10619 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-10619 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-10619 in @sequa-ai/sequa-mcp

Q: How severe is CVE-2025-10619?

CVE-2025-10619 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @sequa-ai/sequa-mcp are affected by CVE-2025-10619?

@sequa-ai/sequa-mcp (npm) versions < 1.0.14 is affected.

Q: Is there a fix for CVE-2025-10619?

Yes. CVE-2025-10619 is fixed in 1.0.14. Upgrade to this version or later.

Q: Is CVE-2025-10619 exploitable, and should I be worried?

Whether CVE-2025-10619 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-10619 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-10619?

Upgrade @sequa-ai/sequa-mcp to 1.0.14 or later.

Summary

@sequa-ai/sequa-mcp has Command Injection vulnerability

Full technical description

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."

Impact

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2025-10619 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.14); upgrading removes the vulnerable code path.

Affected versions

@sequa-ai/sequa-mcp (< 1.0.14)

Security releases

@sequa-ai/sequa-mcp → 1.0.14 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade @sequa-ai/sequa-mcp to 1.0.14 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-10619? CVE-2025-10619 is a medium-severity command injection vulnerability in @sequa-ai/sequa-mcp (npm), affecting versions < 1.0.14. It is fixed in 1.0.14. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
How severe is CVE-2025-10619? CVE-2025-10619 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @sequa-ai/sequa-mcp are affected by CVE-2025-10619? @sequa-ai/sequa-mcp (npm) versions < 1.0.14 is affected.
Is there a fix for CVE-2025-10619? Yes. CVE-2025-10619 is fixed in 1.0.14. Upgrade to this version or later.
Is CVE-2025-10619 exploitable, and should I be worried? Whether CVE-2025-10619 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-10619 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-10619? Upgrade @sequa-ai/sequa-mcp to 1.0.14 or later.