CVE
GPAC crash via NULL pointer dereference in DoWriteMeta
- Exploited
- No known exploitation
- Fix
- Fixed in 26.07.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 26.07.0.
Summary
GPAC, before the fixed release, has a NULL pointer dereference in its MP4Box tool that an attacker can trigger to crash the program. The attacker must supply a crafted ISOBMFF file that has a meta box with an iloc entry but no dref box, and the crash happens when a user runs a rewrite operation such as -unhint on that file.
Original description
GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in DoWriteMeta() in src/isomedia/isom_store.c that allows attackers to crash MP4Box via crafted files. Attackers can supply an ISOBMFF file with a meta box containing an iloc entry but no dref box, crashing MP4Box during rewrite operations like -unhint.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 26.07.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132757 (GPAC before 26.07.0 NULL Pointer Dereference in DoWriteMeta), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132757 (entry last updated 2026-11-18):
Affected:
- gpac gpac: fixed in 26.07.0
Fixed versions: 26.07.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132757 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132757 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/gpac/gpac/commit/758b34ffb17df4d7583b5515241cce67b9278ed9
- https://github.com/gpac/gpac/issues/3666
- https://github.com/gpac/gpac/releases/tag/v26.07.0
- https://github.com/gpac/gpac/blob/v26.02.0/src/isomedia/isom_store.c#L975-L990
- https://www.vulncheck.com/advisories/gpac-before-26.07.0-null-pointer-dereference-in-dowritemeta
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132757
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132757"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- gpac gpac
fixed in 26.07.0
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132757 |
| Record | NVD · CVE-2026-132757 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · sigdevel/pocs · res/gpac/MP4Box/106/106_DoWriteMeta_isomedia_isom_store_c_983 |
| Other links 5 | |
| Patch | GitHub · gpac/gpac · Commit 758b34ff |
| Report | GitHub · gpac/gpac · Issue #3666 |
| Repository | GitHub · gpac/gpac · Release v26.07.0 |
| Repository | GitHub · gpac/gpac · src/isomedia/isom_store.c · L975-L990 |
| Link | vulncheck.com · advisories/gpac-before-26.07.0-null-pointer-dereference-in-dowritemeta |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132757
Is CVE-2026-132757 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132757?
gpac: before 26.07.0.Source: cve.now feed data
How do I fix CVE-2026-132757?
Upgrade to a fixed version: 26.07.0.Source: cve.now feed data