# CVE-2026-54491: Koel: Incomplete fix for CVE-2026-47260 — systemic SSRF in podcast & radio fetch paths

> Authenticated users can exploit SSRF in podcast and radio fetch paths to access internal services or cloud metadata via redirects or DNS rebinding.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-6qvr-wjmv-v8mm

## What is CVE-2026-54491?

CVE-2026-54491 is a high-severity server-side request forgery vulnerability in koel, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Koel is a free, open-source music streaming solution. Prior to 9.7.1, outbound podcast and radio fetch paths perform a point-in-time App\Helpers\Network::isPublicHost() or isSafeUrl() check without pinning the validated address, and most paths lack redirect-hop validation and do not revalidate every redirect target. PhanAn\Poddle\Poddle::fromUrl(), PodcastService::getStreamableUrl(), PodcastService::isPodcastObsolete(), App\Rules\HasAudioContentType, and App\Rules\SafeUrl can therefore follow an attacker-controlled redirect to an internal address or connect after DNS rebinding changes a public resolution to a private one. These paths are reachable through podcast and radio APIs, including createPodcastChannel, createInternetRadioStation, refreshPodcasts, apiResource podcasts, and radio/stations, allowing an authenticated user to request internal services or cloud metadata and potentially receive parsed or streamed response content. This issue is fixed in version 9.7.1.

Weakness: CWE-918 (Server-Side Request Forgery)

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

2 open source packages ship an affected version, including phanan/koel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phanan/koel` | Packagist | All versions | 9.7.1 |
| `phanan/koel` | Packagist | All versions | 9.7.1 |

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

Upgrade phanan/koel to 9.7.1 or later.

## Is CVE-2026-54491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54491 is a high-severity server-side request forgery vulnerability in koel, published on 19 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-54491 exists.

Affected packages and fixed versions:
- phanan/koel (Packagist): affected all versions; fixed in 9.7.1
- phanan/koel (Packagist): affected all versions; fixed in 9.7.1

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

## Sources

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

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