Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-104057 – Unauthenticated Denial of Service – Podgrab (all versions through commit 0322480)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-104057 is an unauthenticated denial-of-service vulnerability in Podgrab, an open-source self-hosted podcast manager (akhilrex/podgrab), caused by unsynchronized concurrent access to shared in-memory maps in the application’s WebSocket handling code. A remote, unauthenticated attacker can crash the Podgrab process by abusing the /ws WebSocket endpoint, forcing operators to manually restart the service. The issue has a CVSS v4.0 score of 8.7 (High) and CWE-362 (Improper Synchronization) classification.

Technical details

  • Root cause: Podgrab maintains two shared Go maps, activePlayers and allConnections, used to track WebSocket client state. These maps are read and written concurrently by the Wshandler and HandleWebsocketMessages goroutines without any mutex or other synchronization primitive protecting them.
  • Trigger conditions: Go’s built-in map type is not safe for concurrent read/write access; when two goroutines access the same map at the same time, the Go runtime detects the data race and raises a fatal, unrecoverable panic that terminates the process (this bypasses normal panic/recover error handling).
  • Attack vector: An attacker opens multiple concurrent WebSocket connections to the /ws endpoint and rapidly sends messages over them in a loop, driving the concurrent map accesses that trigger the crash. No authentication or user interaction is required, and in some configurations the /ws route is reachable even when the instance has Basic Auth/password protection enabled, since it was registered outside the authenticated route group.
  • Impact: Full denial of service — the Podgrab process crashes and does not recover on its own, requiring operator intervention to restart the service.

Affected software

  • akhilrex/podgrab — all versions/builds up to and including commit 032248091294dbf5b6a439a5afd93788a7cc647f

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • Immediate: No official patched release has been published by the project as of disclosure; organizations running Podgrab should monitor the upstream repository (akhilrex/podgrab) for a fix that adds proper synchronization (e.g., sync.RWMutex or sync.Map) around activePlayers and allConnections, and that registers the /ws route under the authenticated route group.
  • If no patch is available: Restrict network access to the Podgrab instance and its /ws WebSocket endpoint to trusted hosts/IPs only (e.g., via firewall rules, VPN, or reverse-proxy access controls), and avoid exposing Podgrab directly to the public internet. Monitor the service for unexpected crashes and consider placing it behind a process supervisor configured for automatic restart to reduce downtime until a fix is applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge