# CVE-2026-130630: GPAC 26.02.0 NULL Pointer Dereference via dasher_configure_pid


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-c4mv-2vq2-w3gx, UBUNTU-CVE-2026-130630

## What is CVE-2026-130630?

CVE-2026-130630 is a medium-severity vulnerability in gpac, published on 17 Nov 2026. 

### Official description

GPAC 26.02.0 contains a NULL pointer dereference vulnerability in dasher_configure_pid() in src/filters/dasher.c that dereferences ds2->set without checking for NULL. Attackers can supply a crafted MPEG-2 TS file processed with MP4Box -dash to disconnect a PID and crash MP4Box, causing denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-130630?

1 open source package ship an affected version, including gpac/gpac.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `gpac/gpac` | GitHub | `pkg:github/gpac/gpac` | From 26.02.0 | 26.07.0 |

## How do I fix CVE-2026-130630?

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-130630 being exploited?

There is no known exploitation of CVE-2026-130630 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130630 and fix it if it is affected.

What it is: CVE-2026-130630 is a medium-severity vulnerability in gpac, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130630 in the wild and no public exploit code.

Affected packages and fixed versions:
- gpac/gpac (GitHub): affected from 26.02.0; fixed in 26.07.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130630/ (Markdown: https://insights.sbomify.com/CVE-2026-130630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130630
- OSV: https://osv.dev/vulnerability/CVE-2026-130630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130630/
Summaries are generated and may contain mistakes; the official description above is the record.
