Local process crash via unchecked TeXML arrays
Published Mar 12, 2026 · Updated Mar 12, 2026
Stack-based buffer overflow in GPAC 26.03-DEV allows local users to crash MP4Box by importing a crafted TeXML file. The txtin_process_texml function writes sharedStyles and marker elements into fixed 50-entry styles and marks stack arrays without checking their counters. Local access to invoke MP4Box on attacker-controlled input is required; the published reproduction demonstrates a sanitizer-detected overflow, not code execution.
Summary
What happened
Stack-based buffer overflow in GPAC 26.03-DEV allows local users to crash MP4Box by importing a crafted TeXML file. The txtin_process_texml function writes sharedStyles and marker elements into fixed 50-entry styles and marks stack arrays without checking their counters. Local access to invoke MP4Box on attacker-controlled input is required; the published reproduction demonstrates a sanitizer-detected overflow, not code execution.
The record
- CVE
- CVE-2026-4015
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-119, CWE-121
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=26.03-DEV
What conditions does exploitation require?
What is affected?
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
- poc_texml_overflow.zipproof of concept · demonstrated
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