# CVE-2025-10619: sequa-ai sequa-mcp OAuth Server Discovery node-oauth-client-provider.ts redirectToAuthorization os command injection

> Attackers can execute arbitrary OS commands via OAuth server discovery if non-default URLs are used, requiring an upgrade to the sequa-mcp library.

- **Severity:** Medium 5.3 (`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/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-9pw5-wx67-q964

## What is CVE-2025-10619?

CVE-2025-10619 is a medium-severity command injection vulnerability in sequa-ai sequa-mcp, published on 17 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-10619?

2 open source packages ship an affected version, including @sequa-ai/sequa-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@sequa-ai/sequa-mcp` | npm | All versions | 1.0.14 |
| `@sequa-ai/sequa-mcp` | npm | All versions | 1.0.14 |

## How do I fix CVE-2025-10619?

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

## Is CVE-2025-10619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10619 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10619 and fix it if it is affected.

What it is: CVE-2025-10619 is a medium-severity command injection vulnerability in sequa-ai sequa-mcp, published on 17 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10619 exists.

Affected packages and fixed versions:
- @sequa-ai/sequa-mcp (npm): affected all versions; fixed in 1.0.14
- @sequa-ai/sequa-mcp (npm): affected all versions; fixed in 1.0.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10619/ (Markdown: https://insights.sbomify.com/CVE-2025-10619/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10619
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10619
- OSV: https://osv.dev/vulnerability/CVE-2025-10619

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10619/
Summaries are generated and may contain mistakes; the official description above is the record.