# CVE-2026-130793: GPAC before 26.07.0 Stack-Based Buffer Overflow via gf_filter_pid_resolve_file_template_ex


- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-qrxj-vrqr-mmxh, UBUNTU-CVE-2026-130793

## What is CVE-2026-130793?

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

### Official description

GPAC before 26.07.0 contains a stack-based buffer overflow vulnerability in gf_filter_pid_resolve_file_template_ex() in src/filter_core/filter_pid.c that allows local attackers to write past fixed GF_MAX_PATH stack buffers. Attackers can convince a user to segment a crafted NHML input referencing an overly long media file name with MP4Box -dash to crash the process.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

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


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

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

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-130793 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- gpac/gpac (GitHub): affected all versions; 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-130793/ (Markdown: https://insights.sbomify.com/CVE-2026-130793/index.md)
```

## Sources

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

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