# CVE-2026-109827: GPAC AIT Parser ait.c gf_m2ts_decode_ait out-of-bounds write

> Remote attackers can trigger an out-of-bounds write in the GPAC AIT parser, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-xg2v-p5jc-x9xf, UBUNTU-CVE-2026-109827

## What is CVE-2026-109827?

CVE-2026-109827 is a medium-severity memory corruption vulnerability in GPAC, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in GPAC up to 26.07.0. This vulnerability affects the function gf_m2ts_decode_ait of the file src/media_tools/ait.c of the component AIT Parser. Such manipulation leads to out-of-bounds write. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 6d2c21a1a688abb20d0111b608db3b6f44d348f4. Applying a patch is advised to resolve this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-109827 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109827 is a medium-severity memory corruption vulnerability in GPAC, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109827 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-109827/ (Markdown: https://insights.sbomify.com/CVE-2026-109827/index.md)
```

## Sources

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

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