Quick answers
- Is CVE-2026-109827 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109827 being exploited in the wild.
- How severe is CVE-2026-109827?
- Medium severity, with a CVSS score of 6.3, published 13 October 2026.
- Which products and versions are affected?
- Gpac up to 26.07.0.
- Is there a fix for CVE-2026-109827?
- Yes: fixed in Fixed in commit 6d2c21a1a688abb20d0111b608db3b6f44d348f4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109827 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-109827?
- Check whether you run Gpac at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Fixed in commit 6d2c21a1a688abb20d0111b608db3b6f44d348f4
Technical details
The gf_m2ts_decode_ait function in src/media_tools/ait.c fails to properly bounds-check the application descriptors loop, allowing an out-of-bounds write when processing specially crafted AIT data. The vulnerability occurs in the application descriptor parsing logic where the loop does not validate that the descriptor index remains within allocated array bounds before writing. An attacker can remotely exploit this via a malformed MPEG-TS stream without requiring authentication or user interaction.
Affected products
- GPAC GPAC up to 26.07.0
Timeline
- 2026-10-13: disclosed