# CVE-2026-132763: GPAC before 26.07.0 Integer Underflow Out-of-Bounds Write in gf_xml_sax_peek_node


- **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:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-3m4h-qvrw-rv6q, UBUNTU-CVE-2026-132763

## What is CVE-2026-132763?

CVE-2026-132763 is a medium-severity vulnerability in gpac, published on 18 Nov 2026. 

### Official description

GPAC before 26.07.0 contains an integer underflow vulnerability in gf_xml_sax_peek_node() that allows attackers to write a zero byte outside the heap line buffer via crafted XML attribute values. Attackers can supply a crafted XMT file with a ROUTE or command referencing an undefined node, imported with MP4Box, to crash the process and corrupt memory.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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

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-132763?

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-132763 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132763 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132763 is a medium-severity vulnerability in gpac, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132763 exists.

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-132763/ (Markdown: https://insights.sbomify.com/CVE-2026-132763/index.md)
```

## Sources

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

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