Skip to main content
VulnerabilityPublished Updated

CVE-2025-15668: GPAC · Heap-based Buffer Overflow

Affects GPACSource CVE Database V5

0
Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 16 Nov 2026, 20:24 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GPACAffected
  • =b40ce70f5
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:gpac:gpac:*:*:*:*:*:*:*:*

AI-suggested

A patch identified by commit f29f955f2a3b5e8e507caad3e52319f961bf37bf is available and should be applied to remediate this vulnerability. Since the vendor advisory or official fix details are not explicitly provided, users should verify and apply the patch from the GPAC source repository or official channels. Until patched, restrict local access to trusted users only.

Description

A vulnerability was identified in GPAC up to b40ce70f5. This issue affects the function sgpd_del_entry of the file src/isomedia/box_code_base.c of the component MP4Box. Such manipulation of the argument data leads to heap-based buffer overflow. Local access is required to approach this attack. The exploit is publicly available and might be used. The name of the patch is f29f955f2a3b5e8e507caad3e52319f961bf37bf. It is advisable to implement a patch to correct this issue.

References

Community reviews

Loading reviews…