Process crash via unchecked SAF stream count
Published Jan 15, 2026 · Updated Jan 15, 2026
Stack-based buffer overflow in GPAC 2.4.0 allows attackers to crash the process by supplying a crafted SAF file. The safdmx_check_dur function indexes a 1,024-entry StreamInfo stack array with an unchecked nb_streams counter while parsing unique stream_id values with ts_res fields. Processing a file with at least 1,025 qualifying stream identifiers writes past the array boundary; the demonstrated consequence is a crash, while code execution was not shown.
Summary
What happened
Stack-based buffer overflow in GPAC 2.4.0 allows attackers to crash the process by supplying a crafted SAF file. The safdmx_check_dur function indexes a 1,024-entry StreamInfo stack array with an unchecked nb_streams counter while parsing unique stream_id values with ts_res fields. Processing a file with at least 1,025 qualifying stream identifiers writes past the array boundary; the demonstrated consequence is a crash, while code execution was not shown.
The record
- CVE
- CVE-2025-70305
- Published
- Jan 15, 2026
- Updated
- Jan 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2026CVE publishedPublication date reported by the CVE source.
- Jan 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GPAC SAF stack out-of-bounds proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo