Vulnerabilities

GPAC v26.07.0, an open-source multimedia framework, contains an out-of-bounds read (CWE-125) in the gf_dm_get_chunk_data function in src/utils/downloader.c. The flaw is triggered when GPAC's HTTP downloader processes a crafted HTTP request/response, for example when a user opens or streams a remote media URL under an attacker's control, causing the application to crash. The impact is limited to denial of service — there is no indication of information disclosure, code execution, or integrity impact (CVSS 3.1: 6.5, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H). Users and automated pipelines running GPAC 26.07.0 that fetch content over HTTP are affected; the issue is fixed in upstream commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640. A public proof of concept exists via a GitHub issue tracker entry, but EPSS is very low (0.2%, 16th percentile), the CVE is not in CISA's KEV, and no exploitation in the wild is known.

Do: Upgrade GPAC to any build containing fix commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640 (post-26.07.0) or apply the patch to downstream packages. Until patched, avoid opening or streaming remote/untrusted HTTP URLs in GPAC and restrict automated pipelines from fetching media from untrusted sources. The flaw is denial-of-service only, so prioritize it below confidentiality/integrity issues, but monitor crashes in downloader code as an indicator of attempted triggering.

MessagePack for Ruby (the msgpack-ruby gem) prior to version 1.8.2 contains a stale-pointer flaw (CWE-416) in MessagePack::Buffer#clear: when the C extension returns an internal read-memory (rmem) page to the shared pool via _msgpack_buffer_shift_chunk, the rmem_last, rmem_end, and rmem_owner fields are left pointing at the freed page. A subsequent Buffer#write on the cleared buffer, combined with a second MessagePack::Buffer in the same process allocating that recycled page, causes both buffers to alias the same memory. An attacker with local access or the ability to influence serialized data in such a process can read or corrupt data belonging to the other buffer; the CVSS 4.0 score of 2.1 assesses the impact as low-severity information disclosure with a local attack vector. Any Ruby application using MessagePack serialization (commonly for caching, RPC, or message handling) on versions before 1.8.2 is affected, but triggering requires a specific clear-then-reuse buffer pattern. No in-the-wild exploitation is known: the flaw is not in CISA KEV, EPSS estimates a 0.2% probability of exploitation within 30 days, and the only public reference is the GitHub advisory GHSA-4mrv-5p47-p938.

Do: Upgrade msgpack-ruby to version 1.8.2 or later. As an interim mitigation, avoid calling MessagePack::Buffer#clear on buffers that are subsequently reused (allocate fresh buffers instead) and audit code paths that clear and reuse MessagePack buffers within a single process. Given the local attack vector, prioritize hosts that run untrusted local code or multi-tenant Ruby processes.

MessagePack is the serializer implementation for Python msgpack.org. Prior to 1.2.1, there is an Out-of-bounds read/crash on Unpacker reuse after a caught error, potentially leading to a DoS attack. If the Unpacker is used repeatedly after an error occurs, the process may crash with a SEGV. This issue has been fixed in version 1.2.1.

A use-after-free in the gf_sei_load_from_state_internal function (/filters/sei_load.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted MPEG-2 TS file.

A buffer overflow in the gf_media_import function (/media_tools/av_parsers.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.

GPAC MP4Box v2.4 was discovered to contain a NULL pointer dereference in the gf_isom_add_track_kind() function at isomedia/isom_write.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.