# CVE-2026-42606: AzuraCast: Password Reset Poisoning via Untrusted X-Forwarded-Host Header Leads to Account Takeover and 2FA Bypass

> Attackers can hijack password reset links via X-Forwarded-Host header to take over accounts and bypass 2FA in AzuraCast.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-gv7r-3mr9-h5x8

## What is CVE-2026-42606?

CVE-2026-42606 is a high-severity vulnerability in AzuraCast, published on 9 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

AzuraCast is a self-hosted, all-in-one web radio management suite. Prior to version 0.23.6, the ApplyXForwarded middleware unconditionally trusts the client-supplied X-Forwarded-Host HTTP header with no trusted proxy allowlist. An unauthenticated attacker can poison the password reset URL sent to any user by injecting this header when triggering the forgot-password flow. When the victim clicks the poisoned link, their reset token is exfiltrated to the attacker's server. The attacker then uses the token on the real instance to reset the victim's password and destroy their 2FA configuration, achieving full account takeover. This issue has been patched in version 0.23.6.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

2 open source packages ship an affected version, including azuracast/azuracast. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `azuracast/azuracast` | Packagist | All versions | 0.23.6 |
| `azuracast/azuracast` | Packagist | All versions | 0.23.6 |

Products: Azuracast Azuracast.

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

Upgrade azuracast/azuracast to 0.23.6 or later.

## Is CVE-2026-42606 being exploited?

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

## Other vulnerabilities in AzuraCast

- [CVE-2026-42605](https://insights.sbomify.com/CVE-2026-42605/): AzuraCast: Path Traversal in `currentDirectory` Parameter Enables Remote Code Execution via Media Upload (high 8.8)
- [CVE-2023-2531](https://insights.sbomify.com/CVE-2023-2531/): Improper Restriction of Excessive Authentication Attempts in azuracast/azuracast (high 7.3)
- [CVE-2023-2191](https://insights.sbomify.com/CVE-2023-2191/): Cross-site Scripting (XSS) - Stored in azuracast/azuracast (low 3.5)
- [CVE-2025-67737](https://insights.sbomify.com/CVE-2025-67737/): AzuraCast Vulnerable to Pre-Auth File Deletion & Admin RCE (low 3.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42606 is a high-severity vulnerability in AzuraCast, published on 9 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42606 exists.

Affected packages and fixed versions:
- azuracast/azuracast (Packagist): affected all versions; fixed in 0.23.6
- azuracast/azuracast (Packagist): affected all versions; fixed in 0.23.6

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-42606/ (Markdown: https://insights.sbomify.com/CVE-2026-42606/index.md)
```

## Sources

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

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