cve.bz

CVE-2026-130797 GPAC through 26.07.0 Uninitialized Variable via Duplicate XMT PROTO Field Names

6.9 medium

Medium (6.9) in gpac gpac.

On this page
GPAC through 26.07.0 contains a use of uninitialized variable vulnerability in xmt_parse_element() that allows local attackers to corrupt memory by supplying duplicate PROTO field names. Attackers can trick a user into opening a crafted XMT file with MP4Box, causing xmt_parse_sf_field() to write through an uninitialized pointer and crash the process.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

6.6 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-457 Use of Uninitialized Variable
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-130797 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-130797?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-130797?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-130797 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gpacthrough 26.07.0

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON