VulnerabilityPublished 7 Aug 2025Updated 8 Aug 2025

CVE-2025-47806: GStreamer · Stack-based Buffer Overflow

Source CVE Database V5

Not known to be exploited · CVSS 5.6 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

5.6Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: GStreamer through 1.26.1

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

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

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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

Immediate mitigation involves updating GStreamer to a version beyond 1.26.1 once a patch addressing CVE-2025-47806 is released. Organizations should monitor official GStreamer repositories and security advisories for patch availability.
Until patches are available, implement input validation and filtering to block or quarantine subtitle files from untrusted or unknown sources, especially SubRip (.srt) files.
Employ sandboxing or containerization for media processing components to limit the blast radius of potential crashes or exploits.
Use application-level monitoring to detect abnormal crashes or memory errors in media playback or processing services, enabling rapid incident response.
For embedded devices, coordinate with vendors to obtain firmware updates or mitigations.
Review and restrict network exposure of services that automatically process subtitle files to reduce remote attack surface.
Educate users and administrators about the risks of opening or streaming media with untrusted subtitles.
Consider disabling subtitle parsing in GStreamer if subtitle functionality is not required, as a temporary risk reduction measure. These steps go beyond generic advice by focusing on controlling input sources, isolating vulnerable components, and proactive monitoring tailored to the specific nature of this vulnerability.

Description

In GStreamer through 1.26.1, the subparse plugin's parse_subrip_time function may write data past the bounds of a stack buffer, leading to a crash.

Impact

For European organizations, the impact of CVE-2025-47806 depends largely on the extent to which GStreamer is integrated into their multimedia processing workflows, streaming platforms, or embedded systems. Media companies, broadcasters, and content delivery networks that rely on GStreamer for subtitle rendering or media playback are at risk of service disruption due to crashes caused by malicious subtitle files. This could lead to denial of service, affecting user experience and operational continuity. In sectors such as telecommunications, automotive infotainment, and consumer electronics manufacturing, where GStreamer is embedded in devices, exploitation could lead to device instability or compromise. Although the CVSS score indicates a medium severity with low confidentiality and integrity impact, the lack of required privileges and user interaction means remote exploitation is feasible if the vulnerable component processes untrusted subtitle files automatically. This could be leveraged in targeted attacks or supply chain compromises. Additionally, organizations handling user-generated content or streaming third-party media should be cautious, as attackers might embed malicious subtitles in media files. The absence of known exploits suggests limited current active threat, but the vulnerability should be addressed proactively to prevent future exploitation. Overall, the impact is moderate but significant for organizations with high reliance on GStreamer-based media processing, especially those in media, telecommunications, and embedded device sectors in Europe.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
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

Description

AI analysisMachine-generated, updated 15 Aug 2025, 01:15 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats