Is CVE-2026-25104 exploited in the wild?

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

How severe is CVE-2026-25104?

High severity, with a CVSS score of 7.8, published 26 May 2026.

Is there a fix for CVE-2026-25104?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-25104 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-25104?

Check whether you run MediaArea MediaInfoLib 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-25104: MediaArea MediaInfoLib heap overflow in LXF parsing

CVE-2026-25104 · Severity: high · CVSS 7.8 · Published 2026-05-26

MediaInfoLib, a library used to extract technical data and metadata from video and audio files, is vulnerable to a memory corruption flaw when processing LEITCH (.lxf) video files. By tricking a user into opening a specially crafted malicious file, an attacker could potentially execute unauthorized code on the system. This could lead to a full system compromise or the theft of sensitive information.

Technologies: MediaArea MediaInfoLib. Vendors: MediaArea.

Quick answers

Is CVE-2026-25104 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25104 being exploited in the wild.
How severe is CVE-2026-25104?: High severity, with a CVSS score of 7.8, published 26 May 2026.
Which products and versions are affected?: MediaArea MediaInfoLib 26.01.
Is there a fix for CVE-2026-25104?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-25104 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-25104?: Check whether you run MediaArea MediaInfoLib 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 heap-based buffer overflow exists in MediaInfoLib 26.01 within the LXF (LEITCH video format) parsing functionality, specifically in the `File_ChannelGrouping::Read_Buffer_Continue()` function. The vulnerability is rooted in an integer underflow (CWE-191) occurring during the audio channel merging process. When processing a 20-bit depth stream, the `Minimum` variable (derived from user-controlled buffer sizes) can be decremented past zero, resulting in a massive unsigned integer value. This causes a `while` loop to continue indefinitely, overwriting heap memory beyond the allocated 32,768-byte buffer. An attacker can leverage this to overwrite adjacent memory structures, including the `BitDepth` variable and subsequent pointers, to achieve arbitrary code execution. Exploitation requires a user to open a malicious .lxf file.

Affected products

MediaArea MediaInfoLib 26.01

Timeline

2026-05-25: advisory: Initial disclosure by Cisco Talos (TALOS-2026-2367)
2026-05-26: disclosed: NVD publication date

References

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