CVE-2026-36911: MPC-BE Division-by-Zero DoS Vulnerability – CVSS 5.5 Medium
A division-by-zero bug in MPC-BE, a popular open-source media player, can be triggered by opening a specially crafted MP4 file. The vulnerability crashes the application, denying service to the user. An attacker would need local access or the ability to trick a user into opening a malicious file, but no special privileges are required.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-369
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-01 / 2026-07-02
NVD description (verbatim)
A division-by-zero vulnerability in the CStreamSwitcherOutputPin::DecideBufferSize function of Aleksoid1978 MPC-BE before commit 4341cb3 allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-36911 is a division-by-zero arithmetic exception in the CStreamSwitcherOutputPin::DecideBufferSize function within Aleksoid1978's MPC-BE media player. The vulnerability stems from insufficient input validation when processing MP4 file headers. When DecideBufferSize performs a calculation that divides by a zero value derived from crafted file metadata, an unhandled exception occurs, causing immediate process termination. The flaw affects MPC-BE versions prior to commit 4341cb3, which implements bounds checking on the divisor before the operation.
Business impact
For organizations that standardize on MPC-BE or distribute it to users, this vulnerability creates a denial-of-service vector. An attacker can distribute a weaponized MP4 file via email, file-sharing platforms, or compromised websites, causing MPC-BE to crash whenever a user attempts to play it. While not a data breach or system compromise risk, repeated crashes degrade user productivity and could be chained with social engineering (e.g., 'video file failed to play, click here for codec update') to deliver secondary payloads. Organizations relying on MPC-BE for media transcoding or playback pipelines should treat this as an operational availability concern.
Affected systems
MPC-BE (Media Player Classic - Black Edition) prior to commit 4341cb3 is vulnerable. MPC-BE is a community-maintained fork of the original Media Player Classic, widely used on Windows systems by power users, media professionals, and organizations needing lightweight playback with advanced codec support. The vulnerability is triggered only when a user attempts to open a malicious MP4 file, so exposure depends on file handling practices and user awareness.
Exploitability
Exploitability is moderate. The attack requires user interaction—specifically, opening a crafted MP4 file in a vulnerable version of MPC-BE. An attacker cannot exploit this remotely without first compromising a system or tricking a user into downloading the file. No authentication or elevated privileges are needed. The CVSS vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) reflects local attack surface, low complexity, no privileges required, but mandatory user interaction. Public exploit code is not known to exist, but the division-by-zero condition is straightforward to reproduce once the triggering MP4 structure is identified.
Remediation
Update MPC-BE to a version incorporating commit 4341cb3 or later. This commit adds validation logic that ensures the divisor is non-zero before performing the calculation in DecideBufferSize. Users should check the official Aleksoid1978 MPC-BE repository (GitHub) for the latest release. Until patching is possible, users should avoid opening MP4 files from untrusted sources and consider disabling MPC-BE as the default handler for MP4 files in environments where file provenance is uncertain.
Patch guidance
Verify the version of MPC-BE installed by checking Help > About or the executable properties. Compare the commit hash or release version against the official Aleksoid1978 repository to confirm commit 4341cb3 or a later build is deployed. For automated environments, check the build timestamp or version string; patched builds will include a fix label or higher version number. If MPC-BE is distributed via organizational package management, update the deployment package and redeploy to affected systems. End-user systems should be prompted to update via the MPC-BE internal update mechanism or manual download from the official source.
Detection guidance
Monitor for repeated MPC-BE process crashes or unexpected termination events in application logs. Endpoint Detection and Response (EDR) tools can flag suspicious MP4 file downloads followed by immediate MPC-BE crashes, suggesting exploitation attempts. Network-level detection is limited since the vulnerability is triggered locally, but security teams can scan inbound file transfers for MP4 files with anomalous headers (e.g., zero-valued size or duration fields in specific atoms). File integrity monitoring can help identify when new MP4 files appear in user directories and correlate with crash events. User reports of 'video won't play' should be triaged to confirm whether a crash dump or event log entry indicates a division-by-zero exception.
Why prioritize this
This vulnerability warrants medium priority in most environments due to its denial-of-service impact and reliance on user interaction. However, organizations should elevate priority if: (1) MPC-BE is mission-critical for media workflows; (2) users frequently receive or share video files from external parties; (3) the organization has limited ability to rapidly patch desktop applications. The absence of data exfiltration, code execution, or privilege escalation risk keeps it from critical tier, but the ease of trigger and potential for user frustration justify timely remediation.
Risk score, explained
The CVSS 3.1 score of 5.5 (MEDIUM) reflects a local attack vector with low complexity and no privilege requirement, but mandatory user interaction and high availability impact. The score appropriately captures that this is a nuisance vulnerability for most users (crashing an application) rather than a system-wide security breach. Organizationally, the risk is elevated if MPC-BE availability is contractually or operationally critical, or if the user base is targeted by social engineering campaigns that combine malicious video files with credential harvesting.
Frequently asked questions
Can this vulnerability be exploited remotely without user action?
No. The vulnerability requires a user to manually open a crafted MP4 file in MPC-BE. An attacker cannot trigger it over the network without first delivering the file to the target system, typically via email, downloads, or file-sharing services. Once the file is opened, the crash is automatic.
Does this vulnerability allow attackers to steal data or run malicious code?
No. CVE-2026-36911 causes only a denial of service (application crash). It does not enable data exfiltration, unauthorized code execution, or system compromise. The division-by-zero exception terminates the MPC-BE process but does not spawn a shell or modify system files.
Which versions of MPC-BE are affected?
All versions prior to commit 4341cb3 are vulnerable. Users should update to the latest release from the official Aleksoid1978 MPC-BE repository on GitHub and verify the commit history to ensure the fix is included. If you are unsure of your version, check Help > About or contact your IT administrator.
What should I do if I encounter a crash while playing an MP4 file?
Update MPC-BE to the latest version immediately. Until you can patch, avoid opening MP4 files from unknown or untrusted sources. If a colleague or external party sends you a video file, verify its legitimacy before opening it. If crashes persist after updating, contact MPC-BE support or your IT helpdesk.
This analysis is based on CVE-2026-36911 as published by official vulnerability databases. SEC.co makes no warranty regarding the completeness or accuracy of third-party vulnerability data. Organizations should verify patch availability and applicability within their own environments and testing procedures before deploying updates. This vulnerability was not included in CISA's Known Exploited Vulnerabilities (KEV) catalog at the time of publication. Exploitation in the wild should be reported to relevant vendors and security authorities. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-55642MEDIUMGPAC MP4Box Floating Point Exception Denial of Service
- CVE-2025-70100MEDIUMlwext4 Divide-by-Zero Denial of Service (MEDIUM)
- CVE-2026-14629MEDIUMRT-Thread Divide-by-Zero Denial of Service Vulnerability
- CVE-2026-46161MEDIUMLinux Kernel RAID10 Divide-by-Zero Denial of Service
- CVE-2026-46184MEDIUMLinux ua101 USB Audio Driver Division-by-Zero Denial-of-Service
- CVE-2026-47152MEDIUMEmberZNet Level Control DoS Vulnerability
- CVE-2026-47153MEDIUMEmberZNet Level Control Divide-by-Zero DoS Vulnerability
- CVE-2026-6683MEDIUMFatFs Divide-by-Zero Denial of Service in exFAT Sync Logic