Cyber Resilience

CVE-2025-70307

Memory Safety in Gpac 2.4.0

Public PoCMemory Safety
Published
15 January 2026
Modified
30 January 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0045 37th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-70307 is a high-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Gpac Gpac. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-70307, published on 2026-01-15, is a stack-based buffer overflow vulnerability (CWE-121) in the dump_ttxt_sample function of GPAC version 2.4.0. The flaw allows attackers to trigger a crash via a crafted packet, earning a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high-impact availability disruption with no confidentiality or integrity effects.

Remote attackers require no privileges or user interaction to exploit the vulnerability over the network with low complexity. By sending a specially crafted packet to a vulnerable GPAC instance, they can cause a denial of service through stack overflow, potentially crashing the application and disrupting multimedia processing or related services.

A proof-of-concept exploit for the vulnerability is publicly available on GitHub at https://github.com/zakkanijia/POC/blob/main/gpac_boxDump/GPAC_tx3g.md. No official advisories or patches are referenced in the available information.

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-121

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52292Same product: Gpac Gpac
CVE-2025-70304Same product: Gpac Gpac
CVE-2025-60474Same product: Gpac Gpac
CVE-2025-55660Same product: Gpac Gpac
CVE-2025-70309Same product: Gpac Gpac
CVE-2023-2837Same product: Gpac Gpac
CVE-2026-27821Same product: Gpac Gpac
CVE-2025-70305Same product: Gpac Gpac
CVE-2024-0321Same product: Gpac Gpac
CVE-2023-4756Same product: Gpac Gpac

Affected Assets

gpac
gpac
2.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can discover stack-buffer overflows before deployment.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from exceeding stack buffer bounds.

SI-16 Memory Protection good match

Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices directly prevent introduction of stack buffer overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.

PR.PS-02 partial match
prevents

Patching eliminates known instances of the weakness after discovery.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing (fuzzing, static analysis) detects stack overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify buffer-size and input-validation rules.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety and least-privilege stack usage.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121

References