CVE-2026-36911
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA division-by-zero vulnerability exists in the CStreamSwitcherOutputPin::DecideBufferSize function of MPC-BE. When processing a specially crafted MP4 file, the function attempts to divide by a value that can be zero (likely related to buffer size calculation), causing the application to crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify MPC-BE is installedCheck common installation paths: C:\Program Files\MPC-BE\, C:\Program Files (x86)\MPC-BE\, or look for mpc-be64.exe/mpc-be.exe in typical locations. Also check Windows Start Menu for MPC-BE entry.Affected if MPC-BE is found on the system
-
Determine installed MPC-BE versionRight-click the MPC-BE executable (mpc-be64.exe or mpc-be.exe), select Properties, go to the Details tab, and read the Product version field. Alternatively, open MPC-BE, go to Help > About to view version information.Affected if The installed version is older than the version containing commit 4341cb3 (the fix)
-
Confirm MP4 playback capabilityMPC-BE supports MP4 playback by default - verify the software can open MP4 files by attempting to open a known MP4 file or checking file associations in the system.Affected if MPC-BE can process MP4 files (this is the default behavior and the code path that triggers the vulnerability)
A user is affected if MPC-BE is installed with a version prior to the fix commit and the software is used to open MP4 files, as the division-by-zero occurs in the CStreamSwitcherOutputPin::DecideBufferSize function when processing such files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate MPC-BE to the version containing commit 4341cb3 or later. As a temporary measure, avoid opening untrusted or unknown MP4 files with the software.
Update to MPC-BE version that includes commit 4341cb3 (any version after this commit)
- 1. Navigate to the official MPC-BE GitHub repository at github.com/aleksoid1978/MPC-BE
- 2. Check the commit history for commit 4341cb3 to identify what version includes the fix
- 3. Download or update to a version of MPC-BE that includes commit 4341cb3 or later
- 4. Verify the installation is complete and test playback functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36911 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data