CVE-2026-71613
Awaiting Analysis Awaiting Analysis - Queue

Buffer Overflow in GPAC via j2kdec_process Function

Vulnerability report for CVE-2026-71613, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-09

Last updated on: 2026-09-10

Assigner: MITRE

Description

Buffer Overflow vulnerability in GPAC c2dee3aff638cd96f9617ac5b17dc2868cd90ef3 allows an attacker to execute arbitrary code via the j2kdec_process() function. Fixed in 9a253a07fd3f6b48022bba74302bf39388dda859.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-09
Last Modified
2026-09-10
Generated
2026-09-30
AI Q&A
2026-09-10
EPSS Evaluated
2026-09-27
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
gpac gpac From c2dee3a (exc)
gpac gpac to 9a253a07fd3f6b48022bba74302bf39388dda859 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-120 The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-71613 is a heap buffer overflow in the GPAC multimedia framework affecting the j2kdec_process function. It occurs when processing a maliciously crafted JP2 file where the header declares small dimensions but the codestream declares large dimensions. This mismatch causes an undersized buffer allocation that is later overflowed by actual pixel data, leading to potential arbitrary code execution or denial-of-service attacks.

Detection Guidance

To detect this vulnerability, monitor for crashes or segmentation faults when processing JP2 files with GPAC. Check for unusually large memory allocations or buffer overflow warnings in logs. Use tools like AddressSanitizer (ASan) or Valgrind to detect heap overflows during file processing. Example commands: 'gpac -i poc.jp2' to test with a crafted file, or 'valgrind --tool=memcheck gpac -i test.jp2' to detect memory issues.

Impact Analysis

This vulnerability allows attackers to execute arbitrary code or crash applications by processing specially crafted JP2 files. Users running vulnerable GPAC versions may experience system instability, unauthorized code execution, or denial-of-service conditions when opening malicious media files.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling denial-of-service attacks or arbitrary code execution. If exploited, it may lead to unauthorized access to sensitive data, violating confidentiality requirements under these regulations. Additionally, the lack of proper input validation could result in data integrity issues, further compromising compliance.

Mitigation Strategies

Immediately update GPAC to the patched version (commit 9a253a07fd3f6b48022bba74302bf39388dda859 or later). Avoid processing untrusted JP2 files, especially those with mismatched dimensions between JP2 headers and JPEG-2000 codestreams. Implement input validation to reject files with inconsistent dimensions. Disable or restrict GPAC in environments where untrusted media processing is required.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71613. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart