Is CVE-2026-79513 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-79513 being exploited in the wild.

How severe is CVE-2026-79513?

Medium severity, with a CVSS score of 6.5, published 9 September 2026.

Is there a fix for CVE-2026-79513?

A patch was published on 2026: Fix committed in commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-79513 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-79513?

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.

CVE-2026-79513: GPAC divide-by-zero in dash_client timeline parsing

CVE-2026-79513 · Severity: medium · CVSS 6.5 · Published 2026-09-09

GPAC is an open-source multimedia framework used to play and stream audio and video content. A flaw in how it processes DASH video streaming manifest files (MPD) can be exploited via a crafted manifest to crash the player, causing a denial of service. An attacker hosting a malicious video stream could render playback unavailable for users connecting to it.

Technologies: Gpac. Vendors: Gpac.

Quick answers

Is CVE-2026-79513 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-79513 being exploited in the wild.
How severe is CVE-2026-79513?: Medium severity, with a CVSS score of 6.5, published 9 September 2026.
Which products and versions are affected?: Gpac v26.07.0.
Is there a fix for CVE-2026-79513?: A patch was published on 2026: Fix committed in commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-79513 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-79513?: 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.

Technical details

A divide-by-zero vulnerability exists in the gf_dash_get_timeline_duration function in src/media_tools/dash_client.c. The DASH MPD parser stores segment duration attributes without validating they are non-zero, then later performs division by this duration value when calculating segment counts, triggering a floating-point exception (SIGFPE). The vulnerability is triggered when a crafted MPD file contains a SegmentTimeline element with d="0" (e.g., <S t="0" d="0" r="-1"/>). An attacker can exploit this via network by hosting a malicious MPD file and directing users to stream from it; no authentication or user interaction beyond clicking a link is required. Successful exploitation crashes the GPAC process. A fix has been committed to the repository (commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640).

Affected products

GPAC GPAC v26.07.0

Timeline

2026-08-19: disclosed: Security issue reported on GitHub
2026-09-09: advisory: CVE-2026-79513 published
2026: patched: Fix committed in commit 2fd5a06ab226767900fd86edb5a1e8bfc1010640

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.