VulnerabilityPublished 17 Feb 2026Updated 23 Feb 2026

CVE-2026-2629: jishi node-sonos-http-api · OS Command Injection

Affects jishi node-sonos-http-apiSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 Feb 2026
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
jishinode-sonos-http-api	Affected =3776f0ee2261c924c7b7204de121a38100a08ca7	Fixed in–

AI-suggested

To mitigate CVE-2026-2629, organizations should first identify all deployments of node-sonos-http-api, particularly those utilizing the TTS Provider on macOS systems. Until an official patch is released, consider disabling the TTS Provider component or restricting its usage to trusted internal networks only. Implement strict input validation and sanitization on the 'phrase' parameter at the application level to prevent injection of malicious commands. Employ network-level controls such as firewall rules or API gateways to limit access to the node-sonos-http-api service, allowing only authorized clients. Monitor logs for unusual command execution patterns or unexpected API requests targeting TTS functionality. Engage with the project maintainers or community to track patch releases and apply updates promptly once available. Additionally, consider containerizing or sandboxing the node-sonos-http-api service to limit the impact of potential exploitation. Regularly audit and update dependencies and conduct security reviews of custom integrations involving this API.

Description

A weakness has been identified in jishi node-sonos-http-api up to 3776f0ee2261c924c7b7204de121a38100a08ca7. Affected is the function Promise of the file lib/tts-providers/mac-os.js of the component TTS Provider. This manipulation of the argument phrase causes os command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-2629 is the potential for remote attackers to execute arbitrary operating system commands on affected systems running node-sonos-http-api with the vulnerable TTS Provider component. This can lead to full system compromise, unauthorized data access or modification, and disruption of service availability. Since the vulnerability requires no authentication or user interaction, it significantly lowers the barrier for exploitation. Organizations using this API in smart home environments or integrated audio control systems may face risks including unauthorized control of devices, lateral movement within internal networks, and potential exposure of sensitive information. The public availability of exploit code increases the likelihood of automated attacks or exploitation by less skilled threat actors. The rolling release nature of the project complicates patch management, potentially prolonging exposure. Overall, the vulnerability poses a moderate to high risk to confidentiality, integrity, and availability of affected systems, especially in environments where node-sonos-http-api is exposed to untrusted networks or internet-facing interfaces.

Summary

CVE-2026-2629 identifies a critical security weakness in the jishi node-sonos-http-api project, a popular Node.js-based API for controlling Sonos speakers. The vulnerability resides in the TTS (Text-To-Speech) Provider component, specifically within the Promise function of the lib/tts-providers/mac-os.js file. The flaw is due to improper sanitization or validation of the 'phrase' argument passed to this function, which is subsequently used in OS command execution contexts. This lack of input validation enables an attacker to inject arbitrary OS commands remotely, leading to command injection attacks. The vulnerability is exploitable over the network without requiring authentication or user interaction, making it highly accessible to attackers. The public availability of exploit code further elevates the risk of exploitation. The CVSS 4.0 vector indicates a network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). This vulnerability can allow attackers to execute arbitrary commands on the host system, potentially leading to system compromise, data theft, or service disruption. The affected component is specifically relevant to macOS environments where TTS functionality is active within node-sonos-http-api deployments.

References

Community reviews

Loading reviews…