AzuraCast cross-station playlist injection in media edit endpoint
- Exploited
- No known exploitation
- Fix
- Fixed in 0.24.1
- Who is exposed
- Specific setups only
Summary
AzuraCast 0.19.0 before 0.24.1 contains an improper authorization vulnerability that allows users with station media rights to add tracks to other stations' playlists by supplying foreign playlist ids to the single-file edit endpoint. Attackers can send sequential playlist ids in the playlists array to inject entries into other stations' AutoDJ rotations and public now-playing metadata, causing failed playback slots.
Who should check
Teams running AzuraCast 0.19.0 through 0.24.0 on multi-station installs where users hold station media rights on one station
“allows users with station media rights to add tracks to other stations' playlists”
What to do
Check whether your setup matches what the bug needs.
AzuraCast version 0.19.0 up to but not including 0.24.1 Attacker must hold station media rights on at least one station, and the injection is sent to the single-file edit endpointUpgrade 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-134356 (AzuraCast 0.19.0 before 0.24.1 Cross-Station Playlist Injection via Media Edit Endpoint), 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-134356 (entry last updated 2026-11-21):
Affected:
- AzuraCast AzuraCast: from 0.19.0, fixed in 0.24.1
Fixed versions: 0.24.1.
Conditions (all must be true for the bug to be hit):
- AzuraCast version 0.19.0 up to but not including 0.24.1 (source: https://www.vulncheck.com/advisories/azuracast-0.19.0-before-0.24.1-cross-station-playlist-injection-via-media-edit-endpoint)
- Attacker must hold station media rights on at least one station, and the injection is sent to the single-file edit endpoint (source: https://www.vulncheck.com/advisories/azuracast-0.19.0-before-0.24.1-cross-station-playlist-injection-via-media-edit-endpoint)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134356 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134356 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-4r56-qj88-h46c
- https://www.vulncheck.com/advisories/azuracast-0.19.0-before-0.24.1-cross-station-playlist-injection-via-media-edit-endpoint
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-134356
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-134356"}.Affected versions
- AzuraCast AzuraCastFrom 0.19.0 · fixed in 0.24.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · AzuraCast/AzuraCast · Advisory GHSA-4r56-qj88-h46c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134356 |
| Record | NVD · CVE-2026-134356 |
| Other links 1 | |
| Link | vulncheck.com · advisories/azuracast-0.19.0-before-0.24.1-cross-station-playlist-injection-via-media-edit-endpoint |
Questions about CVE-2026-134356
Is CVE-2026-134356 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?
Users with station media rights can add their own tracks to playlists on other stations by supplying foreign playlist ids to the single-file media edit endpoint. The injected tracks can enter other stations' AutoDJ rotations and public now-playing metadata, causing failed playback slots. No data from the other station is disclosed.
Source: vulncheck.com
Which versions are affected by CVE-2026-134356?
AzuraCast: from 0.19.0 before 0.24.1.
Source: cve.now feed data
Am I affected, and how do I check?
AzuraCast versions from 0.19.0 up to but not including 0.24.1 are affected. The setup involves an account holding station media rights on at least one station, with requests sent to the single-file edit endpoint. Check your installed version in the AzuraCast admin panel or release information to see whether it falls in that range.
Source: vulncheck.com
How do I fix CVE-2026-134356?
Upgrade AzuraCast to version 0.24.1, which is the fixed version listed for this vulnerability. No patch identifiers or workaround are given in the facts.
Source: vulncheck.com
Related
- CVE-2026-134359AzuraCast before 0.24.1 OS Command Injection via Liquidsoap Annotation Values
- CVE-2026-121429AzuraCast through 0.23.8 Command Injection via StereoTool Liquidsoap pipe()
- CVE-2026-121428AzuraCast through 0.23.8 RCE via Supervisor Configuration Injection in Timezone
- CVE-2026-121427AzuraCast through 0.23.8 Config Injection via frontend_config.custom_config
- CVE-2026-100856AzuraCast before 0.23.6 Code Injection via Remote Relay Password
- CVE-2026-100852AzuraCast before 0.23.8 Command Injection via Streamer Username
No corrections so far. Something wrong on this page? Report an error.