Skip to main content
VulnerabilityPublished

CVE-2025-70309: GPAC · Stack-based Buffer Overflow

Affects GPACSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 08:30 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubGPACpkg:github/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

Since no official patches or updates are currently available, organizations should implement immediate mitigations to reduce exposure. These include: 1) Restricting or sanitizing WAV file inputs to GPAC-based applications, including validating file integrity and format before processing. 2) Employing network-level controls to limit exposure of media processing services to untrusted sources. 3) Monitoring and logging media ingestion activities to detect anomalous or malformed WAV files. 4) Isolating GPAC processing components in sandboxed or containerized environments to contain potential crashes. 5) Updating to newer GPAC versions once patches addressing this vulnerability are released. 6) Reviewing and hardening media processing workflows to minimize automated processing of untrusted media files. 7) Engaging with GPAC maintainers or vendors for timely security updates and advisories. These targeted mitigations go beyond generic advice by focusing on input validation, isolation, and monitoring specific to the WAV file processing context.

Description

A stack overflow in the pcmreframe_flush_packet function of GPAC v2.4.0 allows attackers to cause a Denial of Service (DoS) via a crafted WAV file.

References

Community reviews

Loading reviews…