Skip to main content
Vulnerability Database/CVE-2026-112009

CVE-2026-112009: SMPEG Buffer Overflow Vulnerability

CVE-2026-112009 is a heap buffer overflow in SMPEG library that allows attackers to trigger crashes through crafted MPEG files. This post explains its technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112009 Overview

CVE-2026-112009 is a heap out-of-bounds read vulnerability [CWE-125] in the smpeg MPEG decoding library through version 2.0.0. The flaw resides in the MPEGsystem::FillBuffer() function, which parses MPEG system header stream tables without validating byte values. An attacker who supplies a crafted MPEG file can cause the parser to read past the 16384-byte buffer boundary. Applications that open the file through SMPEG_new, SMPEG_new_rwops, or SMPEG_new_data crash when every stream table byte has its high bit set. The issue affects software projects embedding smpeg for MPEG-1 playback.

Critical Impact

A crafted MPEG file triggers an out-of-bounds read that crashes any application using smpeg's public initialization APIs.

Affected Products

  • smpeg library versions through 2.0.0
  • Applications linking the MPEGsystem component for MPEG-1 system stream parsing
  • Downstream software distributing bundled copies of smpeg

Discovery Timeline

  • 2026-10-18 - CVE-2026-112009 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112009

Vulnerability Analysis

The vulnerability resides in MPEGsystem::FillBuffer() within MPEGsystem.cpp. The function parses the stream table embedded in an MPEG system header without bounding the number of entries it consumes. When each byte in the stream table has its high bit set, the parsing loop continues advancing beyond the fixed 16384-byte read buffer. The result is a heap out-of-bounds read that terminates the host process. Because smpeg is embedded directly into media players and games, the crash propagates to any application that passes the crafted file through SMPEG_new, SMPEG_new_rwops, or SMPEG_new_data.

The VulnCheck advisory and the HackMD analysis both identify the vulnerable code at lines 803-823 of MPEGsystem.cpp in the upstream icculus/smpeg repository. See the HackMD Out-of-Bounds Read Analysis for the full trace.

Root Cause

The root cause is missing input validation on the system header stream table length. The parser treats bytes with the high bit set as continuation markers and advances a pointer for each one. No check compares the pointer against the end of the 16384-byte buffer, so adversary-controlled input dictates how far the loop reads. This matches the [CWE-125] out-of-bounds read pattern common to legacy media parsing code.

Attack Vector

Exploitation requires a local user to open a malicious MPEG file in an application linked against smpeg. The attack requires user interaction, such as opening a file or loading media supplied through a game asset bundle. There is no network attack vector and no public exploit is listed in Exploit-DB. The documented impact is process termination; the advisories do not describe memory disclosure or code execution outcomes.

See the VulnCheck Advisory for smpeg and the GitHub Code Reference for the vulnerable source lines.

Detection Methods for CVE-2026-112009

Indicators of Compromise

  • Unexpected crashes or SIGSEGV termination in processes that load MPEG media through smpeg
  • MPEG files whose system header stream table contains sequences of bytes with the high bit set (0x80 or higher)
  • Core dumps referencing MPEGsystem::FillBuffer in the stack trace

Detection Strategies

  • Inventory applications and packages that statically or dynamically link smpeg 2.0.0 or earlier
  • Scan file repositories and game asset directories for MPEG files sourced from untrusted origins
  • Enable AddressSanitizer in development builds to catch the out-of-bounds read during media loading

Monitoring Recommendations

  • Alert on repeated application crashes correlated with MPEG file opens on endpoints
  • Collect and review crash telemetry for stack frames inside the smpeg library
  • Monitor software bill of materials feeds for downstream packages that bundle smpeg

How to Mitigate CVE-2026-112009

Immediate Actions Required

  • Identify all installed software that embeds smpeg 2.0.0 or earlier and restrict loading of untrusted MPEG content
  • Block or sandbox MPEG files received from external sources until a fixed build is deployed
  • Rebuild dependent applications against a patched smpeg source tree once upstream commits a fix

Patch Information

No vendor patch release is referenced in the advisory data at the time of publication. Monitor the GitHub smpeg Repository for a corrective commit to MPEGsystem.cpp. Downstream maintainers should apply bounds checks on the stream table parsing loop in MPEGsystem::FillBuffer() and rebuild distribution packages.

Workarounds

  • Replace smpeg with a maintained MPEG decoder such as FFmpeg where feasible
  • Run applications that depend on smpeg inside a sandbox or container that limits process impact on crash
  • Pre-validate MPEG system headers with a separate parser before passing files to smpeg APIs
bash
# Identify binaries linked against the smpeg shared library on Linux hosts
ldconfig -p | grep -i smpeg
find / -type f \( -name 'libsmpeg*.so*' -o -name 'smpeg*.dll' \) 2>/dev/null

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.