Quick answers
- Is CVE-2026-121427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121427 being exploited in the wild.
- How severe is CVE-2026-121427?
- High severity, with a CVSS score of 7.5, published 3 November 2026.
- Which products and versions are affected?
- AzuraCast through 0.23.8.
- Is there a fix for CVE-2026-121427?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-121427 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-121427?
- Check whether you run AzuraCast at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in PUT /station/{id}/profile/edit, which properly strips privileged backend_config sections for users lacking Broadcasting permission but fails to sanitize the frontend_config.custom_config field. The stored JSON is written verbatim as key=value lines into sc_serv.conf with insufficient escaping, allowing attackers to inject newlines in keys to add arbitrary directives or directly override sensitive keys like adminpassword, password, and portbase.
Affected products
- AzuraCast AzuraCast through 0.23.8
Timeline
- 2026-10-18: disclosed
- 2026-11-03: advisory