Is itCheck something

No. CVE-2026-96652

Plex Media Server can be forced to send data to attackers

Being used now

Yes. Attackers are using this right now.

People who run Plex Media Server. Used together with other Plex flaws.

What to do

Update Plex Media Server to the latest version.

Confirmed in attacksOct 20, 2026
ProductPlex Media Server
GitHub repos1
Attack likelihood, next 30 days12%

Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.

The official description

Plex Media Server contains a server-side request forgery (SSRF) vulnerability which could allow an attacker using any X-Plex-Token value to include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination. This vulnerability can be chained with CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656.

For your tech helper or AI assistant

A read-only checklist. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.

Read-only check, change nothing, send nothing anywhere.
Is Plex Media Server (CVE-2026-96652) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-96652. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.

Code on GitHub

Repos named after this bug. Some are scanners or write-ups, some are working attack code. Do not run them on a machine you care about.

Sources