Skip to main content
CVE-2025-70310VulnerabilityPublished

CVE-2025-70310: GPAC · n/a

Affects GPACSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubzakkanijia/GPACpkg:github/zakkanijia/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

Organizations should implement several specific mitigations beyond generic advice: 1) Immediately audit all systems and applications that utilize GPAC version 2.4.0 for media processing, especially those handling .ogg files. 2) Restrict or block untrusted or unauthenticated sources from uploading or streaming .ogg files to vulnerable applications. 3) Employ application-layer filtering or sandboxing to isolate media processing components, limiting the impact of potential crashes. 4) Monitor logs and application behavior for crashes or abnormal terminations related to media playback. 5) Engage with GPAC maintainers or vendors for timely patches or updates and plan for rapid deployment once available. 6) Consider deploying runtime memory protection mechanisms such as ASLR, DEP, and heap integrity checks to mitigate exploitation impact. 7) Educate users and administrators about the risks of opening untrusted media files. 8) For embedded systems, ensure firmware updates include patched GPAC libraries. These targeted steps will reduce the attack surface and limit potential DoS impacts.

Description

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

References

Community reviews

Loading reviews…