GPAC MP4Box CVE-2025-55654

Requires the victim to run GPAC MP4Box v2.4 and process an attacker-supplied crafted file through the filter pipeline that reaches gf_filter_pid_get_packet. This is strictly local with user interaction (AV:L/UI:R): the attacker cannot trigger it over a network and must socially engineer or otherwise induce the victim to open/process the malicious file. Limiting factors that reduce real-world risk: impact is confined to a process crash (A:H only; C:N/I:N - no code execution or data compromise), it is version-specific (v2.4), and it depends entirely on the victim choosing to process untrusted input with the tool. No authentication is required (PR:N), but the mandatory local user interaction is the dominant constraint.

This is a low-priority, high-noise issue rather than a genuine emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) scores 5.5 (medium) and explicitly limits impact to availability only - a use-after-free that crashes the MP4Box process, not code execution or data exposure. Every real-world signal reinforces low risk: EPSS is 0.17% (6th percentile), there is no CISA KEV listing, and the attack vector is LOCAL with required user interaction, meaning an attacker cannot reach this remotely - a victim must actively run the vulnerable tool against an attacker-supplied file. The signals are consistent, not conflicting: a medium CVSS driven solely by A:H, very low exploitation probability, and no evidence of active exploitation all point the same direction. The only asterisk is that the affected-product metadata is garbage (CPE and EUVD versions are literal 'n/a'), so scope must be taken from the description ('GPAC MP4Box v2.4') rather than structured data. Bottom line: patch during normal maintenance; this does not warrant emergency prioritization.

An attacker crafts a malformed media file and delivers it to a victim (e.g., as a download or email attachment) who processes it with GPAC MP4Box v2.4. When MP4Box's filter pipeline handles the file, gf_filter_pid_get_packet dereferences a freed PID packet, crashing the process and denying service. No public exploit is flagged in the input, though the upstream issue tracker (gpac/gpac#3249) likely contains a reproducer file.