Quick answers
- Is CVE-2026-36911 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-36911 being exploited in the wild.
- How severe is CVE-2026-36911?
- Informational severity, with a CVSS score of 0, published 1 July 2026.
- Which products and versions are affected?
- Aleksoid1978 MPC-BE before commit 4341cb3.
- Is there a fix for CVE-2026-36911?
- 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-36911 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-36911?
- Check whether you run Aleksoid1978 MPC-BE 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 division-by-zero vulnerability exists in the CStreamSwitcherOutputPin::DecideBufferSize function of MPC-BE. The flaw is triggered when the application processes a malformed MP4 file that contains unexpected values in the stream metadata, leading to an unhandled arithmetic exception. An attacker can exploit this by tricking a user into opening a crafted MP4 file, resulting in an immediate application crash (Denial of Service). The issue was addressed in commit 4341cb3.
Affected products
- Aleksoid1978 MPC-BE (Media Player Classic Black Edition) before commit 4341cb3
Timeline
- 2026-07-01: advisory: CVE-2026-36911 published
- 2026-07-01: disclosed