Skip to content
Applications

CVE-2026-76836

8.7
High
EPSS 0.33%Patch availableAug 25, 2026

Profile permission allows writing Liquidsoap config leading to OS command execution

common questions

Is CVE-2026-76836 being exploited?

Not confirmed. CVE-2026-76836 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-76836?

CVE-2026-76836 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76836?

Yes. A fix has been recorded for CVE-2026-76836. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76836 affect?

CVE-2026-76836 affects AzuraCast backend, Liquidsoap .liq scripts, PUT /api/station/{station_id}/profile/edit endpoint, Server hosting AzuraCast. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76836?

Revoke profile-edit rights, block/restrict the profile-edit API, and apply vendor patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
AzuraCast backendLiquidsoap .liq scriptsPUT /api/station/{station_id}/profile/edit endpointServer hosting AzuraCast
impact

Authenticated users with Station Profile permission can inject Liquidsoap config that executes OS commands on the backend during restart (remote command execution).

action required

Immediate action required

affected versions
AzuraCast AzuraCast
  • affected<= 0.23.8

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free