CVE-2026-96655
Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability
Description
CVE-2026-96655 is a server-side request forgery (SSRF) vulnerability in Plex Media Server that lets an authenticated user make the server issue HTTP requests to arbitrary internal or external addresses through the /video/:/transcode/universal path parameter. Because the request originates from the Plex Media Server itself, it reaches destinations the attacker cannot normally touch — services on the same host, devices on the home or corporate LAN behind the firewall, and cloud metadata endpoints. All Plex Media Server releases before 1.43.3.10861 are affected by CVE-2026-96655. CISA has added this Plex Media Server SSRF vulnerability to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, with a remediation deadline of November 3, 2026.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| plex | media server | < 1.43.3.10861 |
References
- https://forums.plex.tv/t/plex-media-server/30447/711(Release Notes)
- https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json(Third Party Advisory)
- https://www.cve.org/CVERecord?id=CVE-2026-96655(Third Party Advisory, VDB Entry)
- https://zmain.info/blog/plex2shell(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96655(US Government Resource)
Weakness Type
CWE-918: Server-Side Request Forgery (SSRF)
Server-side request forgery occurs when an application fetches a remote resource from a user-supplied URL without validating the destination, so an attacker can redirect the request to a network location of their choosing. In Plex Media Server, a URL value passed in the /video/:/transcode/universal path parameter is used to build an outbound request without a destination allowlist, which turns the media server into a proxy for reaching internal services that network controls were meant to shield.
Learn more: CWE-918 — Server-Side Request Forgery (SSRF)
Impact Analysis
CVE-2026-96655 carries a CVSS 3.1 base score of 4.3 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Attack Vector (Network) and Attack Complexity (Low) mean the SSRF is remotely reachable and easy to trigger — a single crafted request to the transcode endpoint is enough. Privileges Required (Low): any authenticated Plex user, including a shared-library guest rather than the server administrator, can send it, and no user interaction is required. Confidentiality (Low), Integrity (None), Availability (None): the direct damage is limited to information the forged request discloses, which is why the base score stays in the medium band. The practical risk, however, depends on what sits behind the Plex server: on a home network that is the router admin interface and other appliances; in a hosted or cloud deployment it can be a metadata service that hands out credentials. The EPSS score of 0.22% is low, but CVE-2026-96655 is part of the same Plex Media Server vulnerability set as the arbitrary file write CVE-2026-96656, and SSRF is typically used as the reconnaissance step of a longer chain rather than as the final objective.
Exploit Maturity
CISA has added CVE-2026-96655 to the Known Exploited Vulnerabilities catalog, which confirms exploitation in the wild; the entry does not flag ransomware usage. The vulnerability was disclosed together with the other Plex Media Server defects covered in the public "plex2shell" write-up, so the affected endpoint and the shape of the request are documented publicly even where no packaged exploit tool is distributed. With an EPSS score of 0.22% (12th percentile), broad automated exploitation of this specific SSRF is not yet widespread, which fits its role as a stepping stone rather than a headline bug. The realistic scenario to plan against is chaining: an authenticated user employs CVE-2026-96655 to map internal services from the Plex host, then pivots to a more damaging flaw such as the arbitrary file write CVE-2026-96656 on the same unpatched server.
Remediation
- Carry out the action CISA requires. Apply mitigations in accordance with Plex's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline for CVE-2026-96655 is November 3, 2026.
- Upgrade Plex Media Server to 1.43.3.10861 or later, as published in the Plex release notes. All builds before that version are vulnerable; the same upgrade also closes the other Plex Media Server issues disclosed alongside it.
- Review who holds an account on the server. Since a low-privileged authenticated user is enough, remove stale shared-library users and guests, revoke sharing invitations that are no longer needed, and sign out devices to invalidate tokens that may be in unknown hands.
- Constrain the server's outbound reach. Place the Plex host in a network segment that cannot route to management interfaces, hypervisors, or cloud metadata addresses such as 169.254.169.254, and apply egress filtering so that a forged request has nowhere valuable to go even if the endpoint is reachable.
- Watch for reconnaissance and harden the pattern. Review proxy and firewall logs for outbound connections from the Plex host to internal RFC 1918 ranges, loopback addresses or unusual external hosts; for any service you build yourself, validate user-supplied URLs against an allowlist of permitted domains and schemes, block private and link-local ranges, and re-validate after DNS resolution to defeat rebinding.
Technical Details
Plex Media Server accepts a URL value inside the /video/:/transcode/universal path parameter and uses it to construct an outbound request without restricting the destination to the intended media sources, which is the textbook CWE-918 mechanism. The request is then executed by the server process, carrying the server's network position and any implicit trust that internal services grant to it, so the attacker effectively borrows the Plex host's vantage point to probe or read from addresses their own client could never reach. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N shows why this is scored as medium rather than high: the endpoint is network-reachable and deterministic but requires an authenticated session, and what returns to the attacker is limited information disclosure, with no integrity or availability impact on the Plex server itself. The scope remains unchanged in CVSS terms even though the forged request crosses a network boundary, because the affected and impacted components are both the Plex Media Server process.
Frequently Asked Questions
Is CVE-2026-96655 being actively exploited?
Yes. CISA has added CVE-2026-96655 to the Known Exploited Vulnerabilities catalog, which reflects confirmed exploitation in the wild and sets a federal remediation deadline of November 3, 2026. There is no record of use in ransomware campaigns, and the EPSS score of 0.22% indicates that mass automated exploitation of this particular SSRF has not been observed.
What products are affected by CVE-2026-96655?
CVE-2026-96655 affects Plex Media Server in all versions before 1.43.3.10861. The flaw is in the server's /video/:/transcode/universal endpoint, so only the server component is affected, not Plex client applications. Servers running 1.43.3.10861 or later are fixed.
How do I fix CVE-2026-96655?
Upgrade Plex Media Server to 1.43.3.10861 or newer, which removes the unvalidated destination handling in the transcode endpoint. As interim measures, prune unnecessary user accounts and shared-library guests, since exploitation requires an authenticated session, and restrict what the Plex host can reach outbound so a forged request cannot touch management interfaces or cloud metadata services.
How severe is CVE-2026-96655?
CVE-2026-96655 is rated Medium with a CVSS 3.1 base score of 4.3, because the direct impact is limited information disclosure with no integrity or availability damage, and an authenticated account is required. Its EPSS score of 0.22% places it in the 12th percentile for exploitation likelihood. The severity rating understates the operational risk where the Plex server sits on a network with sensitive internal services, and the KEV listing makes patching non-optional regardless of the score.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.