Gpac: Use After Free
CVE-2025-60464 is a high-severity use after free vulnerability in Gpac, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 26.02.0 as the first without the flaw, so updating Gpac to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Gpac to 26.02.0 or a later version.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
A use-after-free in the gf_sei_load_from_state_internal function (/filters/sei_load.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted MPEG-2 TS file.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
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.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- 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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/gpac/gpac/commit/8f404bd581e455267482f86272169a742f654b97
- infosec.exchange/@sigdevel/116778370895014131Exploit, Third Party Advisory
Technical write-ups (may include proof of concept)
- github.com/gpac/gpac/issues/3278Exploit, Issue Tracking
- github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/32/32_filters_sei_load_c_225_in_gf_sei_load_from_state_int…Exploit
- github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/32/README.mdExploit
- openwall.com/lists/oss-security/2026/06/26/4Exploit, Mailing List, Third Party Advisory
Other vulnerabilities in Gpac
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
Recent Use After Free vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
- 8.2 High severity
- 7.8 High severity
Spotted an error? Tell us.