rootpwn

high · CVSS v3 7.6 · CVSS v4 7.2 · EPSS 0.00207

CVE-2026-100851

AzuraCast versions prior to 0.23.8 expose a broken access control flaw in the /api/station/{id}/vue/profile endpoint. Authenticated users wi

Overview

AzuraCast versions prior to 0.23.8 expose a broken access control flaw in the /api/station/{id}/vue/profile endpoint. Authenticated users with only view permissions can retrieve plaintext Icecast/Shoutcast admin, source, and relay passwords. This allows attackers to gain administrative access to the streaming server.

Description

AzuraCast before 0.23.8 contains a broken access control vulnerability in the GET /api/station/{id}/vue/profile endpoint that allows authenticated users with only View Station Page permission to read Icecast/Shoutcast admin, source, and relay passwords. Attackers with View-only access can call this endpoint and receive plaintext frontend credentials in the JSON response, then use the admin password to authenticate to the Icecast admin interface without Broadcasting permission.

Impact

Confidentiality: credentials exposed. Integrity: attackers can modify streaming configuration. Availability: potential disruption. Impacted: administrators and operators of AzuraCast deployments with view-only users.

Remediation

Apply the 0.23.8 update or later. If immediate patching is not possible, revoke view-only permissions or block the endpoint via firewall or reverse proxy.

Risk context

High severity but low EPSS (0.00207) indicates a low likelihood of exploitation, yet the impact warrants timely patching.

Affected products

  • AzuraCast 0.23.7 and earlier

Scores

Severity
high
CVSS v2
8
CVSS v3
7.6
CVSS v4
7.2
EPSS
0.00207

AzuraCast AccessControl CredentialExposure Icecast HighSeverity Patch Defender

← All CVEs

Related CVEs

high

CVE-2026-100744

A flaw has been found in coollabsio Coolify up to 4.1.2. The affected element is an unknown function of the file app/Http/Middleware/CanUpdateResource.php of the component Route-Level Middleware. Executing a manipulation can lead to missing authorization. The attack may be launched remotely. The exploit has been published and may be used. Upgrading to version 4.2.0 is sufficient to fix this issue. This patch is called 39ae16de4248075de8c08f3259114e064b20d52d. It is advisable to upgrade the affected component.

View analysis

high

CVE-2025-71423

Edgelesssys Contrast is a confidential-computing runtime for Kubernetes. In versions 1.9.0 before 1.12.2, the initializer logs the full NewMeshCert response — which contains the workload secret — to standard output at INFO level. As a result, workload secrets are exposed to any Kubernetes user with get or list permission on pods/logs. Because workload secrets are used for encrypted storage and Vault integration, those must also be considered compromised. This is a regression of GHSA-h5f8-crrq-4pw8.

View analysis

high

CVE-2025-71425

Contrast (Edgeless Systems) before 1.8.1 logs the workload secret to stderr, and thus to Kubernetes logs, when the Contrast initializer is configured with CONTRAST_LOG_LEVEL set to info or debug. Because info is the default, all installations that do not customize the initializer log level are affected. This exposes workload secrets — normally accessible only to the Contrast Coordinator, the initializer, the seedshare owner, and the workload owner — to Kubernetes users with get or list permission on pods/logs and to anyone with read access to the Kubernetes log storage, such as the cloud provider. Deployments that do not use workload secrets are unaffected.

View analysis

high

CVE-2025-71426

Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.4.1, a recovering Coordinator does not verify the seed supplied by the recovering party. An attacker can therefore stand up a rogue Coordinator whose manifest passes validation but whose secret seed is attacker-controlled. If network traffic is redirected from the legitimate Coordinator to the attacker's Coordinator, a workload owner can be impersonated when they either set a new manifest without comparing the returned root CA certificate against the existing one (the default behavior of the contrast CLI) or verify the Coordinator without comparing the root CA certificate against a trusted reference. Under these conditions the attacker can issue certificates that chain back to the rogue Coordinator's root CA and recover arbitrary workload secrets of workloads deployed after the attack. Secrets of the legitimate Coordinator (seed, workload secrets, CA), workload integrity, and certificates chaining to the mesh CA are not affected.

View analysis