AzuraCast through 0.23.8 Command Injection via StereoTool Liquidsoap pipe()
AzuraCast 0.23.8 and earlier are affected on stations whose backend has StereoTool installed and configured. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. AzuraCast version 0.23.8 or earlier is affected. The station backend must have StereoTool installed and configured. The StereoTool binary must be installed.
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 45 if CISA's SSVC rates it automatable
CVE-2026-121429 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects AzuraCast; no fixed version is listed yet.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
AzuraCast through 0.23.8 contains a command injection vulnerability that allows station users with Profile permission to execute OS commands via StereoTool settings. Attackers can inject shell metacharacters into stereo_tool_configuration_path or stereo_tool_license_key, which are executed via /bin/sh on station restart, compromising the container.
What to do
Check whether your setup matches what the bug needs.
AzuraCast version 0.23.8 or earlier is affected. The station backend must have StereoTool installed and configured. The StereoTool binary must be installed.Workaround: The checked facts list no fix. While waiting, the most direct way to limit exposure is to remove StereoTool from stations that do not need it, since the flaw depends on StereoTool being installed and configured.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AzuraCast AzuraCast
through 0.23.8
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121429
Is CVE-2026-121429 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in how AzuraCast passes settings to StereoTool through Liquidsoap's pipe() lets crafted input inject operating system commands. Successful use would run commands as the AzuraCast/Liquidsoap process user, which could give access to AzuraCast data and possibly the whole container.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-121429?
AzuraCast: through 0.23.8.Source: cve.now feed data
Am I affected, and how do I check?
AzuraCast version 0.23.8 or earlier is affected, but only on stations whose backend has the StereoTool binary installed and configured. To check, look at the AzuraCast version shown in the web interface or the release tag in use, and check whether StereoTool is installed for a station's backend.Source: vulncheck.com, github.com
How do I fix CVE-2026-121429?
The checked facts do not name a fixed release, so no upgrade target is confirmed here. Check the AzuraCast project's advisory for a patched version before deciding on an upgrade.Source: vulncheck.com, github.com
What if there's no patch?
The checked facts list no fix. While waiting, the most direct way to limit exposure is to remove StereoTool from stations that do not need it, since the flaw depends on StereoTool being installed and configured.Source: vulncheck.com, github.com