Skip to main content
CVE-2025-7797VulnerabilityPublished

CVE-2025-7797: GPAC · NULL Pointer Dereference

Affects GPACSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubgpac/gpacpkg:github/gpac/gpacOther threatsAffected
  • =2.0
  • =2.1
  • =2.2
  • =2.3
  • =2.4
Fixed in–

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

AI-suggested

To mitigate CVE-2025-7797, European organizations should prioritize the following actions: 1) Immediately apply the official patch identified by commit 153ea314b6b053db17164f8bc3c7e1e460938eaa to all affected GPAC versions (2.0 through 2.4). 2) Conduct an inventory to identify all systems and applications using GPAC, including embedded devices and third-party software that may bundle GPAC components. 3) Implement network-level protections such as web application firewalls (WAFs) or intrusion prevention systems (IPS) to detect and block malformed requests targeting the vulnerable function, especially if patching cannot be immediately applied. 4) Monitor logs and network traffic for unusual patterns or crashes related to media streaming services. 5) Establish robust incident response procedures to quickly isolate and remediate affected systems in case of exploitation. 6) Engage with software vendors and service providers to confirm patch deployment and assess exposure. 7) Consider deploying runtime application self-protection (RASP) or sandboxing techniques for media processing components to limit the impact of potential crashes. These steps go beyond generic advice by focusing on comprehensive asset identification, layered defenses, and proactive monitoring tailored to the nature of the vulnerability.

Description

A vulnerability was found in GPAC up to 2.4. It has been rated as problematic. Affected by this issue is the function gf_dash_download_init_segment of the file src/media_tools/dash_client.c. The manipulation of the argument base_init_url leads to null pointer dereference. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The patch is identified as 153ea314b6b053db17164f8bc3c7e1e460938eaa. It is recommended to apply a patch to fix this issue.

References

Community reviews

Loading reviews…