CVE-2026-36910
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 · uneditedAn access violation in the BaseSplitterFile::Read 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 · high confidenceAn access violation vulnerability exists in the BaseSplitterFile::Read function of MPC-BE media player. The vulnerability is triggered when parsing a specially crafted MP4 file, causing an out-of-bounds read or null pointer dereference that leads to a denial of service condition.
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 installationCheck for MPC-BE executable in typical installation paths: C:\Program Files\MPC-BE\mpc-be.exe (Windows) or search for the binary using system file search toolsAffected if MPC-BE executable is found on the system
-
Determine installed MPC-BE versionRight-click the mpc-be.exe file, select Properties, then view the Details tab to see the File Version, or run 'mpc-be.exe /?' to display version information from the command lineAffected if The displayed version number is lower than the version containing the fix from commit 4341cb3
-
Identify vulnerable componentLocate the splitter library files that handle MP4 parsing, typically named mpcparsers.dll or similar splitter DLLs in the MPC-BE installation directoryAffected if The splitter parser component exists and handles MP4 file decoding
-
Verify MP4 file handling is enabledMPC-BE automatically attempts to parse MP4 files when opened; no explicit configuration toggle exists - the vulnerability triggers upon opening a crafted MP4 fileAffected if MPC-BE can be used to open MP4 files, meaning the MP4 parsing functionality is present
The system is affected if MPC-BE media player is installed and the installed version predates the fix from commit 4341cb3, enabling the vulnerable BaseSplitterFile::Read function to parse MP4 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 · scopedUsers should avoid opening untrusted MP4 files until the fix from commit 4341cb3 is applied. Update MPC-BE to the latest version containing the patched code.
Latest MPC-BE stable release (verify version includes commit 4341cb3)
- 1. Visit the official MPC-BE GitHub repository at github.com/Aleksoid1978/MPC-BE
- 2. Navigate to the releases section to identify the latest stable release
- 3. Download and install the latest version of MPC-BE
- 4. Alternatively, verify if commit 4341cb3 is included in your current version by checking the application's version information
- 5. If your version predates the fix, upgrade to the most recent release which should contain the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36910 — 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-36910 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