Plex Media Server SSRF actively exploited (CVE-2026-96652) [PoC]

Actively exploited in the wild - CVE-2026-96652 is a medium-severity server-side request forgery (SSRF) flaw in Plex Media Server before 1.43.3.10861 that lets an attacker force the server to send POST requests to any destination they choose. Patched in 1.43.3.10861 - update immediately.

Overview

Plex Media Server exposes a /player/timeline endpoint that accepts a protocol parameter. In affected versions, that parameter is not restricted to a safe set of values. An attacker can supply a full URL instead of a protocol name, and the Plex server will treat it as the target and issue a POST request to it.

The authorization check on this endpoint accepts any value in the X-Plex-Token header, not just a valid token. That means no account, no valid credential, and no user interaction are required. A remote attacker with network access to the server can trigger the request.

This is a classic SSRF pattern: the server becomes a proxy for the attacker. Because the request originates from the Plex host, it can reach internal services that are not exposed to the internet, and it carries the server’s network position and any implicit trust that comes with it.

Impact

The direct consequence is that an attacker can make the Plex server send crafted POST requests to arbitrary internal or external hosts. Practical abuse includes:

• Probing internal networks and cloud metadata endpoints that only the Plex host can reach.
• Triggering state-changing actions on internal services that trust requests from the local network.
• Using the Plex server as an anonymizing relay for requests to third-party systems.

The CVSS score is 5.3 (network, low complexity, low privileges, no user interaction). The impact is scoped to what the reachable destinations allow, but SSRF frequently escalates when internal admin interfaces or metadata services are in reach.

CISA has added this CVE to its Known Exploited Vulnerabilities catalog, confirming real-world use. The EPSS score remains low at 0.2%, so mass automated scanning is not yet the main driver. Treat the KEV listing as the signal, not the probability estimate.

Remediation and mitigation

1. Upgrade to Plex Media Server 1.43.3.10861 or later. This is the only complete fix.
2. If immediate upgrade is not possible, restrict network access to the Plex web and API ports so only trusted clients can reach them. Do not expose the server directly to the internet.
3. Block outbound traffic from the Plex host to internal management ranges and cloud metadata addresses (for example 169.254.169.254) at the firewall or egress policy.
4. Review Plex server logs for unusual POST requests or connections to unexpected destinations, and check for signs of internal reconnaissance.

Security Insight

Plex has a track record of SSRF-class issues in its media-facing endpoints, and this one repeats the same root pattern: an input that should be an enum accepts a full URL, and a token check accepts any string. That combination suggests endpoint hardening is done per-route rather than enforced by shared middleware. For defenders, the lesson is that a media server sitting on a flat home or office network is a pivot point, and its outbound traffic deserves the same scrutiny as any internet-facing service. Breach reports are available at breach reports and ongoing coverage at security news.

Further Reading

• All Medium Vulnerabilities
• Recent Critical Vulnerabilities
• Top Critical CVEs