cve.bz

CVE-2026-130836 GPAC before 26.07.0 Invalid Pointer Free in gf_sg_command_del()

6.9 medium

Medium (6.9) in gpac gpac.

On this page
GPAC before 26.07.0 contains an invalid pointer free vulnerability in gf_sg_command_del() in src/scenegraph/commands.c that allows attackers to corrupt the heap via crafted XMT scene files. Attackers can supply an XMT-A file whose command field_ptr references the embedded new_node member, causing free() on an interior address and crashing MP4Box.

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-763 Release of Invalid Pointer or Reference
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-130836 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-130836?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-130836?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-130836 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
gpacbefore 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