CVE-2026-76836

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 29, 2026

Advisory Details (5)

Auto-updated Aug 24, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

AzuraCast through 0.23.8 Liquidsoap Configuration Write via Profile Edit Serialization Group Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/azuracast-through-liquidsoap-configuration-write-via-profile-edit-serialization-group-bypass
generic

AzuraCast/backend/src/Entity/Station.php at 0.23.8 · AzuraCast/AzuraCast · GitHub

https://github.com/AzuraCast/AzuraCast/blob/0.23.8/backend/src/Entity/Station.php
generic

AzuraCast/backend/src/Radio/Backend/Liquidsoap/ConfigWriter.php at 0.23.8 · AzuraCast/AzuraCast · GitHub

https://github.com/AzuraCast/AzuraCast/blob/0.23.8/backend/src/Radio/Backend/Liquidsoap/ConfigWriter.php
generic

GitHub - AzuraCast/AzuraCast: A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations. · GitHub

https://github.com/AzuraCast/AzuraCast
github Patch Available🟡 PoC Available

Unauthorized Write to Liquidsoap Custom Config via Profile Edit Endpoint Leads to RCE · Advisory · AzuraCast/AzuraCast · GitHub

https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-q8wg-3qg7-8pc7

Vendor Advisories for CVE-2026-76836(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:44 UTCGHSA enrichment
  3. 2026-08-29 12:03 UTCEG score recompute
  4. 2026-08-29 12:02 UTCGHSA enrichment
  5. 2026-08-29 02:12 UTCEG score recompute
  6. 2026-08-29 02:11 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 13:27 UTCGHSA enrichment
  9. 2026-08-28 00:45 UTCEG score recompute
  10. 2026-08-28 00:45 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 11:55 UTCGHSA enrichment
  13. 2026-08-26 23:13 UTCEG score recompute
  14. 2026-08-26 23:13 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 10:31 UTCGHSA enrichment
  17. 2026-08-25 21:49 UTCEG score recompute
  18. 2026-08-25 21:49 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 09:08 UTCEG score recompute
  21. 2026-08-25 09:08 UTCGHSA enrichment
  22. 2026-08-24 20:26 UTCEG score recompute
  23. 2026-08-24 20:26 UTCGHSA enrichment
  24. 2026-08-24 20:11 UTCEG score recompute
  25. 2026-08-24 20:11 UTCGHSA enrichment
Show 3 more
  1. 2026-08-24 18:21 UTCEG score recompute
  2. 2026-08-24 17:51 UTCEG score recompute
  3. 2026-08-24 17:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76836?
CVE-2026-76836 is a high vulnerability published on August 24, 2026. AzuraCast exposes the Liquidsoap custom configuration fields through an endpoint that does not require the permission guarding them. The backendconfig property in backend/src/Entity/Station.php is annotated with GROUPGENERAL, and PUT /api/station/{stationid}/profile/edit in…
When was CVE-2026-76836 disclosed?
CVE-2026-76836 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76836 actively exploited?
CVE-2026-76836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76836?
CVE-2026-76836 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-76836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76836

Explore →

Is Your Infrastructure Affected by CVE-2026-76836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.