VulnerabilityPublished 7 Dec 2025

CVE-2025-14204: TykoDev cherry-studio-TykoFork · OS Command Injection

Affects TykoDev cherry-studio-TykoForkSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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 7 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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 or the CVSS exploit maturity 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
TykoDev cherry-studio-TykoFork	Affected =0.1	Fixed in–

AI-suggested

To mitigate CVE-2025-14204, European organizations should prioritize the following actions: 1) Monitor TykoDev's official channels for security patches or updates addressing this vulnerability and apply them promptly once available. 2) If patches are not yet available, consider disabling or restricting access to the /.well-known/oauth-authorization-server endpoint or the OAuth Server Discovery component to prevent exploitation. 3) Implement strict input validation and sanitization on the authorizationUrl parameter to block malicious command injection payloads. 4) Employ network-level controls such as firewalls or web application firewalls (WAFs) to detect and block suspicious requests targeting the vulnerable endpoint. 5) Conduct thorough audits of OAuth implementations to identify and remediate insecure configurations. 6) Limit exposure by restricting access to the affected service to trusted internal networks where possible. 7) Enhance monitoring and logging to detect anomalous activities indicative of exploitation attempts. 8) Educate development and security teams about secure coding practices to prevent similar injection flaws in future software versions.

Description

CVE-2025-14204 is a medium-severity OS command injection vulnerability in TykoDev's cherry-studio-TykoFork version 0.1. It affects the redirectToAuthorization function within the OAuth Server Discovery component, specifically the /. well-known/oauth-authorization-server endpoint. An attacker can remotely manipulate the authorizationUrl argument to execute arbitrary OS commands without authentication or user interaction. Although the vulnerability has been publicly disclosed, no known exploits are currently observed in the wild. The CVSS 4.0 base score is 5.3, reflecting the moderate impact and ease of exploitation. European organizations using this product, especially those relying on OAuth services, may face risks of system compromise or data exposure.

Impact

For European organizations, this vulnerability poses a moderate risk, particularly for those deploying TykoDev cherry-studio-TykoFork 0.1 in their OAuth infrastructure. Successful exploitation could allow attackers to execute arbitrary OS commands remotely, potentially leading to unauthorized access, data leakage, or disruption of authentication services. This could compromise sensitive user credentials or internal systems relying on OAuth for identity management. Given the widespread use of OAuth in enterprise environments across Europe, any disruption or compromise could have cascading effects on business operations and data privacy compliance, including GDPR obligations. However, the medium CVSS score and lack of known exploits in the wild suggest the immediate threat level is moderate. Organizations with exposed instances of the vulnerable component are at higher risk, especially if they have not implemented compensating controls such as network segmentation or input validation. The absence of authentication requirements for exploitation increases the attack surface, making internet-facing deployments particularly vulnerable.

References

Community reviews

Loading reviews…