PinePods podcast server can be tricked into reading internal network data
A logged-in user can add a podcast whose episode link points at the server's own internal services. The server fetches that link for them and saves the response, so they can read data they should never see.
| Severity | CriticalCVSS 9.1 of 10 |
|---|---|
| Being exploited? | UnclearNo reports either way yet |
| Fix available? | YesVersion 0.9.0 · since 30 Oct 2026 |
| How sure is this? | Official sourceBacked by an official source |
How the attack works simplified
- 1Logged-in userHas a normal account on the server
- 2Add malicious feedEpisode link points to internal address
- 3Server fetches URLNo check on destination; redirects followed
- 4Response savedStored in downloaded episodes
- 5Attacker reads itInternal data retrieved
- ResultInternal data exposed to a low-privilege user
What happened
In PinePods before 0.9.0, the add_podcast and download_podcast API endpoints store RSS enclosure URLs without validating the destination host or IP, and the server follows redirects, enabling authenticated server-side request forgery (SSRF) to loopback, private-network and cloud metadata addresses.
Are you affected?
You are affected if you run PinePods older than 0.9.0 with server downloads enabled (the default) and self-service signup or any untrusted user accounts.
PinePods versions prior to 0.9.0
What to do
- Update PinePods to version 0.9.0 or later
- If you cannot update immediately, disable server downloads or restrict who can create accounts
- Review downloaded episode records for unexpected internal content and rotate any cloud credentials if metadata access is suspected
Timeline
- 30 Oct 2026, 20:17 UTCPublicly disclosed
- 30 Oct 2026, 20:17 UTCReported by NVD · NVD
- 30 Oct 2026, 20:20 UTCPicked up by Zero Radar
Sources 1 report, oldest first
Official vendor, government CERT or advisory database
- CVE-2026-55598NVD · 30 Oct 2026, 20:17 UTC
Technical details
- ID
- CVE-2026-55598
- CVSS
- 9.1 / 10
- Disclosed
- 30 Oct 2026, 20:17 UTC
- On Zero Radar
- 30 Oct 2026, 20:20 UTC (3 min after disclosure)
- Last change
- 30 Oct 2026, 20:20 UTC
The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works