Skip to content
Fencer Intel
medium 6.6

CVE-2026-130792 json

GPAC before 26.07.0 Heap Buffer Overflow via XML SAX Parser Entity Handling

published yesterday modified yesterday also EUVD-2026-127281

cvss
6.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

GPAC before 26.07.0 contains an integer underflow in gf_xml_sax_parse_intern() in src/utils/xml_parser.c that causes a heap-based buffer overflow when completing partially buffered entities. Attackers can convince a user to process a crafted XML or XMT file with MP4Box, overflowing xml_sax_append_string() size arithmetic to corrupt heap memory and crash the process.

Patch / fix

Is CVE-2026-130792 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-18).

Exploits and checks

  • github.com https://github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/79/79_xml_sax_append_string_xml_parser_c_993.xml referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/86/86_xml_sax_swap_utils_xml_parser_c_214 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
CNA 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
CNA 4.0 6.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • gpac gpac

Classification

Weakness
  • CWE-191 Integer Underflow (Wrap or Wraparound)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.