VulnerabilityPublished 17 Sep 2025

CVE-2025-10619: sequa-mcp · OS Command Injection

Affects sequa-mcpSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.0.14 : update sequa-mcp when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.9% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.14

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
sequa-ai sequa-mcp	Affected =1.0.0 =1.0.1 =1.0.2 =1.0.3 =1.0.4 =1.0.5 =1.0.6 =1.0.7 =1.0.8 =1.0.9 =1.0.10 =1.0.11 =1.0.12 =1.0.13	Fixed in–

AI-suggested

European organizations should immediately upgrade sequa-ai sequa-mcp to version 1.0.14 or later, as this version includes the necessary validation to restrict URLs and prevent command injection. Until the upgrade is applied, organizations should implement strict network segmentation and firewall rules to limit access to the OAuth server discovery component, restricting it to trusted internal IPs only. Monitoring and logging of requests to the redirectToAuthorization function should be enhanced to detect anomalous or unexpected URL inputs that could indicate exploitation attempts. Additionally, organizations should conduct code reviews or penetration testing focused on OAuth-related components to identify any similar injection flaws. Employing runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious OS command patterns in inputs may provide temporary mitigation. Finally, organizations should ensure that incident response teams are prepared to investigate potential exploitation attempts and have backups and recovery procedures in place to restore affected systems promptly.

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

For European organizations using sequa-ai sequa-mcp, particularly in identity and access management or OAuth-based authentication infrastructures, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized command execution on critical authentication servers, undermining the integrity and availability of authentication services. This may result in unauthorized access to protected resources, data breaches, or disruption of business operations. Given the remote exploitability without authentication, attackers could leverage this vulnerability as an entry point into corporate networks. The impact is heightened for organizations relying on sequa-mcp in sensitive sectors such as finance, healthcare, or government, where OAuth servers often protect critical applications and data. Additionally, the vulnerability could be exploited to pivot attacks internally, compromising other systems. The medium CVSS score reflects limited impact scope but does not diminish the importance of timely remediation, especially in environments with high security requirements or regulatory compliance obligations prevalent in Europe (e.g., GDPR).

Summary

CVE-2025-10619 is a medium-severity OS command injection vulnerability found in the sequa-ai sequa-mcp product, specifically affecting versions 1.0.0 through 1.0.13. The vulnerability resides in the redirectToAuthorization function within the src/helpers/node-oauth-client-provider.ts file, part of the OAuth Server Discovery component. The flaw allows an attacker to manipulate input parameters that are used in OS command execution without proper sanitization or validation, leading to command injection. This can be exploited remotely without authentication or user interaction, as the vulnerable function accepts URLs that are not properly validated. The vendor notes that the server is intended to be used only with their own URLs that provide valid responses, but if an attacker supplies a non-sequa URL, this opens a valid attack vector. The vulnerability is publicly disclosed and an exploit could be developed or is potentially available, although no known exploits in the wild have been reported yet. The vendor has released version 1.0.14 which mitigates the issue by enforcing validation to ensure only approved URLs can be opened, effectively preventing injection. The CVSS 4.0 base score is 5.3, reflecting a medium severity with network attack vector, low attack complexity, no privileges or user interaction required, and limited impact on confidentiality, integrity, and availability. This vulnerability is critical to address in environments using sequa-mcp for OAuth server discovery, as it could allow attackers to execute arbitrary OS commands on the server hosting the component, potentially leading to system compromise or lateral movement within the network.

References

Community reviews

Loading reviews…