# CVE-2026-121427: AzuraCast through 0.23.8 Config Injection via frontend_config.custom_config


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-2wcv-vv3g-g86q, GHSA-jv23-j2cr-92x9

## What is CVE-2026-121427?

CVE-2026-121427 is a high-severity vulnerability in AzuraCast, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-15 (External Control of System or Configuration Setting)

## Which versions are affected by CVE-2026-121427?


## How do I fix CVE-2026-121427?

No fix has been published for CVE-2026-121427 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121427 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121427 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121427 and fix it if it is affected.

What it is: CVE-2026-121427 is a high-severity vulnerability in AzuraCast, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121427 exists.

Affected product: AzuraCast. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121427/ (Markdown: https://insights.sbomify.com/CVE-2026-121427/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121427
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121427
- OSV: https://osv.dev/vulnerability/CVE-2026-121427

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121427/
Summaries are generated and may contain mistakes; the official description above is the record.
