CVE-2026-1418
BaseFortify
Publication date: 2026-01-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gpac | gpac | to 2.4.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1418 is an out-of-bounds write vulnerability in the GPAC multimedia framework, specifically in the function gf_text_import_srt_bifs() which processes SRT subtitle files. The function converts subtitle text into a UTF-8-like format and writes it into a fixed-size stack buffer without proper bounds checking. When processing crafted subtitle files containing many non-UTF8 bytes, the output expands beyond the buffer size, causing a buffer overflow. This can lead to memory corruption and potential crashes or exploitable conditions when importing malicious subtitle files locally. [1, 3, 4]
How can this vulnerability impact me? :
This vulnerability can lead to memory corruption in the GPAC multimedia framework when processing maliciously crafted subtitle files. The out-of-bounds write may cause application crashes or create exploitable conditions that could compromise the integrity and availability of the system running GPAC. Exploitation requires local access and can be triggered by importing specially crafted SRT subtitle files. [1, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running GPAC's MP4Box tool with AddressSanitizer (ASan) or UndefinedBehaviorSanitizer (UBSan) enabled. These sanitizers will report runtime errors indicating out-of-bounds writes when processing crafted SRT subtitle files containing many invalid UTF-8 bytes (e.g., lines with many 0xFF bytes). A reproducible test involves creating a VRML scene file referencing an SRT file with a subtitle line containing a large number of 0xFF bytes and running the command: `MP4Box -mp4 scene_bifs.bt -out test.mp4`. The sanitizers will then report the out-of-bounds write error. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to apply the available patch identified by commit 10c73b82cf0e367383d091db38566a0e4fe71772, which adds UTF-8 validation to abort processing of malformed subtitle lines and refactors the subtitle import function to prevent out-of-bounds writes. Until the patch is applied, avoid importing SRT subtitle files containing malformed or non-UTF8 sequences with GPAC versions up to 2.4.0. Additionally, running MP4Box with sanitizers can help detect attempts to exploit this vulnerability. [2]