Skip to main content
CVE-2026-132769VulnerabilityPublished

GPAC before 26.07.0 contains a type confusion vulnerability in xmt_parse_script_field() that allows attackers to

Affects gpacSource GCVE Database

0
Compare
Authoritative record:CVE-2026-132769· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 26.07.0 when convenient.

Data as of 19 Nov 2026, 02:05 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.16.1
Patch
Available – fixed in 26.07.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade gpac/gpac to 26.07.0.

Affected software

ProductAffectedFixed in
GitHubgpac/gpacpkg:github/gpac/gpacOther threatsAffected
  • <26.07.0
Fixed in
  • 26.07.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade GPAC to version 26.07.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated.

Description

GPAC versions prior to 26.07.0 have a type confusion vulnerability in the xmt_parse_script_field() function. This flaw allows attackers to craft a malicious XMT file with duplicate Script field names of conflicting types, causing a heap out-of-bounds read. When such a file is imported using MP4Box, it triggers a crash in the application due to improper handling of single-value fields as multi-value fields. The vulnerability is fixed in version 26.07.0.

References

Community reviews

Loading reviews…