CVE-2026-36909
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 NULL pointer dereference in the AP4_TkhdAtom::GetTrackId() 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 confidenceA NULL pointer dereference vulnerability exists in the AP4_TkhdAtom::GetTrackId() function of the MPC-BE media player. When parsing a specially crafted MP4 file, the code attempts to access a NULL pointer, causing the application to crash and result in a Denial of Service.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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 installedSearch for the mpc-be.exe file in common installation directories such as C:\Program Files\MPC-BE or C:\Program Files (x86)\MPC-BE, or use the Start menu search to locate MPC-BE.Affected if MPC-BE executable is found on the system
-
Determine MPC-BE versionRight-click on mpc-be.exe, select Properties, then go to the Details tab to view the Product version, or right-click MPC-BE in the Start menu and check Properties.Affected if Version cannot be determined or is older than the fixed version
-
Compare version to fixed referenceThe vulnerability was fixed in the version containing commit 4341cb3. Compare your installed version against this reference point. If your version predates this commit, it contains the vulnerability.Affected if Installed version is older than the version containing commit 4341cb3
-
Confirm MP4 file handling is possibleVerify that MPC-BE has the capability to parse MP4 files by checking file associations or simply by attempting to play a standard MP4 file. The flaw triggers during MP4 parsing.Affected if MPC-BE can open and parse MP4 files
A system is affected if MPC-BE is installed with a version that predates the commit 4341cb3 fix and the application is used to open 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 · scopedUpdate MPC-BE to the version containing commit 4341cb3 or later. Until an official patch is available, exercise caution when opening MP4 files from untrusted sources, as malformed track header (tkhd) atoms can trigger the NULL dereference.
Upgrade to the MPC-BE release that includes commit 4341cb3 or later (check GitHub releases for the specific version number)
- 1. Identify the current MPC-BE version in use by checking About/Help in the application
- 2. Navigate to the official MPC-BE GitHub repository at github.com/Aleksoid1978/MPC-BE
- 3. Review the commit history to locate commit 4341cb3 and determine which release version includes this fix
- 4. Download and install the release version that includes commit 4341cb3 or a later stable release
- 5. Verify the installation by checking the version number in the application
- 6. Test playback of MP4 files to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36909 — 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-36909 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