Skip to main content
Menu
CVEs

AzuraCast command injection in Liquidsoap annotation values

CVE-2026-134359Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.24.1
Who is exposed
Specific setups only

Summary

AzuraCast before 0.24.1 fails to escape backslashes in Liquidsoap annotation values, allowing media managers to break out of quoted annotation strings. Attackers can set a crafted ID3 title ending in a backslash to inject a process: protocol URI, achieving OS command execution in the Liquidsoap container during playback.

Who should check

Operators running AzuraCast 0.23.8 or earlier with Liquidsoap-based stations, and anyone granting station Media permissions to users.

Not fixed by: Restricting the Media permission reduces exposure but does not remove the flaw.

“Confirmed affected range: <= 0.23.8”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    AzuraCast 0.23.8 or earlier is affected. Default AzuraCast and Liquidsoap installation is enough; no non-default configuration is needed. Liquidsoap's process: protocol is enabled by default and not restricted by AzuraCast.
  2. Upgrade to a fixed version: 0.24.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134359 (AzuraCast before 0.24.1 OS Command Injection via Liquidsoap Annotation Values), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134359 (entry last updated 2026-11-21):
Affected:
- AzuraCast AzuraCast: fixed in 0.24.1
Fixed versions: 0.24.1.
Conditions (all must be true for the bug to be hit):
- AzuraCast 0.23.8 or earlier is affected. (source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-mf65-hj88-hvrw)
- Default AzuraCast and Liquidsoap installation is enough; no non-default configuration is needed. (source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-mf65-hj88-hvrw)
- Liquidsoap's process: protocol is enabled by default and not restricted by AzuraCast. (source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-mf65-hj88-hvrw)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134359 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134359 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-mf65-hj88-hvrw
- https://www.vulncheck.com/advisories/azuracast-before-0.24.1-os-command-injection-via-liquidsoap-annotation-values
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134359
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134359"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · AzuraCast/AzuraCast · Advisory GHSA-mf65-hj88-hvrw
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134359
RecordNVD · CVE-2026-134359
Other links 1
Linkvulncheck.com · advisories/azuracast-before-0.24.1-os-command-injection-via-liquidsoap-annotation-values

Questions about CVE-2026-134359

Is CVE-2026-134359 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. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

AzuraCast passes values from its own settings into Liquidsoap annotations without proper escaping, so a crafted value can make Liquidsoap run arbitrary operating system commands. The commands run inside the Liquidsoap process context, which allows file reads, file writes and disruption of the broadcast process.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134359?

AzuraCast: before 0.24.1.

Source: cve.now feed data

Am I affected, and how do I check?

AzuraCast 0.23.8 and earlier are affected, and the issue needs only a default AzuraCast and Liquidsoap installation with no non-default configuration. To check a version, look at the AzuraCast release shown in the admin panel or the installed release tag, and compare it with 0.24.1.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134359?

Upgrade AzuraCast to version 0.24.1 or later, which is the listed fixed version.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.