# CVE-2026-4015: GPAC TeXML File load_text.c txtin_process_texml stack-based overflow

> A stack-based buffer overflow in GPAC's TeXML parser allows local attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-4015, GHSA-vj6f-22mx-v35f, UBUNTU-CVE-2026-4015

## What is CVE-2026-4015?

CVE-2026-4015 is a medium-severity memory corruption vulnerability in GPAC, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in GPAC 26.03-DEV. Affected is the function txtin_process_texml of the file src/filters/load_text.c of the component TeXML File Parser. Executing a manipulation can lead to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been made available to the public and could be used for attacks. This patch is called d29f6f1ada5cc284cdfa783b6f532c7d8bd049a5. Applying a patch is advised to resolve this issue.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

No fix has been published for CVE-2026-4015 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4015 is a medium-severity memory corruption vulnerability in GPAC, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4015 exists.

Affected product: GPAC. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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