Cloudanix VulnDB

CVE-2026-17072

Low · 3.3

CVSS

3.3

EPSS

0.1%

Published

Jul 28, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A media playback library can leak tiny amounts of memory data if someone opens a specially crafted video or audio file.

Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Moderate
Impact
Data Exposure
Component
Library
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Heap-based out-of-bounds read of 4 bytes during FLAC audio header parsing in Matroska or WebM containers due to an incomplete boundary check, resulting in limited disclosure of adjacent heap memory.

Why it matters to the business

Low-risk information disclosure if users open malicious media files; minimal operational disruption given the local attack vector, user interaction requirement, and small memory leak size.

How an attack unfolds

An attacker crafts a malicious Matroska or WebM file embedding malformed FLAC headers that bypass the vulnerable boundary check. The victim is tricked into opening the file with an application using the affected GStreamer gst-plugins-good component, triggering the out-of-bounds read and leaking a small amount of heap data.

How to fix it

Upgrade gst-plugins-good to a version containing the corrected boundary check for FLAC header parsing in Matroska/WebM containers. Restrict playback of untrusted media files and apply sandboxing where feasible.

How to confirm the fix worked

Confirm gst-plugins-good version is newer than the vulnerable release and test with known malformed Matroska/WebM samples to verify the out-of-bounds condition no longer occurs.

Typical attack path

  1. Craft a Matroska or WebM container with malformed FLAC headers sized to trigger the incomplete boundary check
  2. Distribute the file via email, download, or removable media to targeted users
  3. Victim opens the file in a vulnerable media player or application relying on GStreamer
  4. Parser performs the 4-byte out-of-bounds read and potentially leaks adjacent heap memory

How to detect it

Review application logs and crash reports from media players for FLAC header parsing errors in Matroska or WebM files; look for unexpected memory access patterns or small information leaks during file processing.

What your security team should do

  • Apply available GStreamer updates across all systems that process media files
  • Enforce policies to block or sandbox playback of media from untrusted sources
  • Monitor for future updates given the 90-day publication window and stable low EPSS

The record

A flaw was found in GStreamer's gst-plugins-good. A heap-based out-of-bounds read of 4 bytes can occur when parsing FLAC audio stream headers embedded in a Matroska or WebM container file. The vulnerability is triggered by a boundary check that does not account for the full size of the data being copied, allowing a small read past the end of the allocated buffer. An attacker could exploit this by crafting a malicious Matroska or WebM file and tricking a user into opening it, potentially leaking a small amount of adjacent heap memory.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities