CVE-2025-34158VulnerabilityPublished 21 Aug 2025Updated 2 Jan 2026

CVE-2025-34158: Plex Media Server · Incorrect Resource Transfer Between Spheres

Affects Plex Media ServerSource CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Plex Media Server	Affected =1.41.7	Fixed in–

AI-suggested

1. Immediately upgrade Plex Media Server to version 1.42.1 or later, where the vulnerability is fixed. 2. Restrict network access to Plex management interfaces (/myplex/account and /api/resources endpoints) using firewall rules or network segmentation to limit exposure to trusted users and systems only. 3. Implement strong authentication and authorization controls for Plex server access, ensuring that only necessary personnel have privileges. 4. Monitor server logs for unusual access patterns or repeated requests to the vulnerable endpoints that could indicate exploitation attempts. 5. Employ network intrusion detection systems (NIDS) with signatures or heuristics targeting suspicious Plex API activity. 6. Educate administrators about the risks of credential exposure and encourage regular credential rotation. 7. If possible, isolate Plex servers in dedicated network zones to reduce lateral movement risk. 8. Conduct regular vulnerability scans and penetration tests focusing on media server infrastructure to detect similar misconfigurations or vulnerabilities.

Description

Plex Media Server (PMS) 1.41.7.x through 1.42.0.x before 1.42.1 is affected by incorrect resource transfer between spheres because /myplex/account provides the credentials of the server owner (and a /api/resources call reveals other servers accessible by that server owner).

Impact

For European organizations using Plex Media Server, this vulnerability could lead to unauthorized disclosure of server owner credentials, enabling attackers to access private media content and potentially pivot to other servers managed by the same owner. This could compromise confidentiality of sensitive or proprietary media, violate privacy regulations such as GDPR, and damage organizational reputation. The integrity of media content could be partially affected if attackers modify accessible resources. While availability is not directly impacted, the breach of trust and potential for further exploitation could lead to service disruptions or data loss indirectly. Organizations relying on Plex for internal media distribution or collaboration may face increased risk of insider threats or external attackers gaining footholds within their network. The vulnerability's network-based exploitability and lack of user interaction requirement increase the risk of automated attacks or worm-like propagation within vulnerable environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Jan 2026, 23:51 UTC

WeaknessesCWE-669

Technical details

References

Community reviews

Related threats