# CVE-2026-76836: AzuraCast through 0.23.8 Liquidsoap Configuration Write via Profile Edit Serialization Group Bypass

> Station managers can bypass permission checks to inject malicious Liquidsoap configurations, leading to remote code execution on the server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-53mh-vf3g-pggg, GHSA-q8wg-3qg7-8pc7

## What is CVE-2026-76836?

CVE-2026-76836 is a high-severity missing authorization vulnerability in AzuraCast, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AzuraCast exposes the Liquidsoap custom configuration fields through an endpoint that does not require the permission guarding them. The backend_config property in backend/src/Entity/Station.php is annotated with GROUP_GENERAL, and PUT /api/station/{station_id}/profile/edit in backend/src/Controller/Api/Stations/ProfileEditController.php deserializes with that group while requiring only StationPermissions::Profile. AbstractArrayEntity::fromArray() then assigns every public property with no field-level permission check, so custom_config_top, custom_config, custom_config_pre_playlists, custom_config_pre_live, custom_config_pre_fade and custom_config_bottom are writable through it. ConfigWriter::writeCustomConfigurationSection() emits those values verbatim into the generated Liquidsoap .liq script, where the process.run() and process.exec() built-ins execute operating system commands when the backend restarts, which the built-in sync task triggers automatically once needs_restart is set. The dedicated endpoint for the same data, PUT /api/station/{id}/liquidsoap-config, requires StationPermissions::Broadcasting, so a station manager holding only the profile permission reaches configuration that the intended boundary reserves for broadcasting operators.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-76836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76836 is a high-severity missing authorization vulnerability in AzuraCast, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76836 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-76836/ (Markdown: https://insights.sbomify.com/CVE-2026-76836/index.md)
```

## Sources

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

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