Quick answers
- Is CVE-2026-110936 exploited in the wild?
- Yes. CVE-2026-110936 is known to be exploited in the wild, first recorded on 20 October 2026. Treat it as urgent.
- How severe is CVE-2026-110936?
- Critical severity, with a CVSS score of 4.3, published 23 September 2026.
- Which products and versions are affected?
- Plex Media Server before 1.43.3.10861.
- Is there a fix for CVE-2026-110936?
- A patch was published on 2026-09-23: Fixed in version 1.43.3.10861 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110936 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-110936?
- Check whether you run Plex Media Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The /player/timeline endpoint accepts a protocol parameter that is not properly validated, allowing an attacker to inject arbitrary URLs. The vulnerability requires any valid X-Plex-Token (which may be obtained through various means or shared tokens), and can be exploited over the network to force the Plex server to make outbound POST requests to attacker-controlled or internal network destinations, enabling SSRF attacks.
Affected products
- Plex Media Server before 1.43.3.10861
Identifiers
- CVE-2026-110936
- CVE-2026-96655
- CVE-2026-96656
- CVE-2026-96654
- CVE-2026-96652
- CVE-2026-106931
Timeline
- 2026-09-23: disclosed
- 2026-09-23: patched: Fixed in version 1.43.3.10861