CVE-2025-70305: GPAC · n/a
Affects GPACSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubzakkanijia/GPACpkg:github/zakkanijia/GPACOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately inventory and identify all systems running GPAC version 2.4.0 within your environment, focusing on media processing and streaming infrastructure. 2. Restrict or block the ingestion and processing of .saf files from untrusted or unauthenticated sources to reduce exposure to crafted malicious files. 3. Implement input validation and file integrity checks on .saf files before processing to detect malformed or suspicious content. 4. Monitor application logs and system stability for crashes or anomalies related to GPAC processes, enabling early detection of exploitation attempts. 5. Isolate media processing environments where possible to contain potential denial of service impacts. 6. Engage with the GPAC vendor or community to track the release of patches or updates addressing this vulnerability and apply them promptly once available. 7. Educate users and administrators about the risks of opening untrusted .saf files and enforce strict file handling policies. 8. Consider deploying application-level sandboxing or containerization for GPAC processes to limit the impact of crashes on broader systems. 9. Develop incident response plans specific to media processing disruptions to ensure rapid recovery and continuity.
Description
A stack overflow in the dmx_saf function of GPAC v2.4.0 allows attackers to cause a Denial of Service (DoS) via a crafted .saf file.