CVE-2025-65407VulnerabilityPublished 1 Dec 2025

CVE-2025-65407: live555 · n/a

Affects live555Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Dec 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
GitHubrgaufman/live555`pkg:github/rgaufman/live555`Other threats	Affected =2018.09.02	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Restrict and validate all incoming MPEG Program streams, especially those from untrusted or external sources, to prevent processing of maliciously crafted streams. 2. Implement network-level filtering and intrusion detection systems to monitor for abnormal MPEG stream traffic patterns indicative of exploitation attempts. 3. Employ application-level sandboxing or process isolation for services using Live555 to contain crashes and prevent wider system impact. 4. Monitor application logs and system stability closely for signs of crashes or instability related to MPEG stream processing. 5. Engage with vendors or maintainers of Live555 to obtain patches or updates addressing this vulnerability as soon as they become available. 6. Consider temporary workarounds such as disabling MPEG1or2Demux functionality if feasible without disrupting critical services. 7. Educate operational teams about the risk and ensure incident response plans include procedures for handling DoS events related to streaming media. 8. Regularly update and patch all related software components to minimize exposure to known vulnerabilities.

Description

CVE-2025-65407 is a use-after-free vulnerability in the MPEG1or2Demux::newElementaryStream() function of Live555 Streaming Media v2018.09.02. An attacker can exploit this by supplying a crafted MPEG Program stream, causing a Denial of Service (DoS) condition. The vulnerability does not impact confidentiality or integrity but can disrupt availability by crashing affected services. Exploitation requires no privileges but does require user interaction to process the malicious stream. No known exploits are currently in the wild, and no patches have been published yet. The CVSS score is 6.5 (medium severity), reflecting the moderate impact and ease of exploitation. European organizations using Live555 for streaming media processing are at risk, especially those in media, broadcasting, and telecommunications sectors.

Impact

The primary impact of CVE-2025-65407 is a Denial of Service condition caused by application crashes when processing malicious MPEG Program streams. For European organizations, this can disrupt media streaming services, video conferencing, and surveillance systems that rely on Live555 Streaming Media. The unavailability of these services can lead to operational downtime, loss of customer trust, and potential financial losses, especially in sectors like broadcasting, telecommunications, and public safety. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized data modifications are not expected. However, repeated exploitation could degrade service reliability and availability. The ease of exploitation (network vector, no privileges) increases the risk, particularly for organizations that accept MPEG streams from untrusted or external sources. The lack of patches means organizations must rely on mitigations until an official fix is released. Given the widespread use of Live555 in European media infrastructure, the impact could be significant if exploited at scale.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 19:11 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats