Skip to main content
VulnerabilityPublished

CVE-2025-70302: gpac · Heap-based Buffer Overflow

Affects gpacSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jan 2026

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubgpac/gpacpkg:github/gpac/gpacOther threatsAffected
  • =2.4.0
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-70302, organizations should first identify all instances of GPAC version 2.4.0 in their environments, including embedded systems, media servers, and development environments. 2) Employ runtime protections such as heap memory protection mechanisms (e.g., ASLR, DEP) and enable compiler-based security features if recompiling GPAC from source. 3) Isolate GPAC processes in sandboxed or containerized environments to limit the impact of potential crashes. 4) Monitor logs and system behavior for crashes or anomalies related to media processing components. 5) Engage with the GPAC development community or vendors for updates and patches, and plan for timely upgrades once fixes are released. 6) For critical services, consider fallback or redundancy mechanisms to maintain availability during potential exploitation attempts. 7) Educate developers and operators about safe handling of untrusted media inputs to reduce attack surface.

Description

A heap overflow in the ghi_dmx_declare_opid_bin() function of GPAC v2.4.0 allows attackers to cause a Denial of Service (DoS) via a crafted input.

References

Community reviews

Loading reviews…