NULL Pointer DereferenceWeakness · CWE-476

CVE-2026-36912

HIGH · 7.5 CVSS v3.1 Published 2026-07-01

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click 8 weeks old

Official description

NVD · unedited

A NULL pointer dereference in the AP4_AtomSampleTable::GetSample() function of Aleksoid1978 MPC-BE before commit 4341cb3 allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.

Technical summary

dbcve analysis · moderate confidence

A NULL pointer dereference exists in the AP4_AtomSampleTable::GetSample() function when parsing MP4 files. When a crafted MP4 file is processed, the function attempts to access a NULL pointer, causing the application to crash and resulting in a Denial of Service.

MitigationUpdate MPC-BE to the version containing commit 4341cb3 or later, which includes the fix for the NULL pointer dereference in the MP4 sample table parsing code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if MPC-BE or Bento4 (AP4) library is in use

Check installed programs for MPC-BE media player, or look for binaries named 'libap4' or 'Bento4' in the system. Search program directories for files containing 'AP4_AtomSampleTable' in binary strings.

Affected if MPC-BE or any application using the Bento4 MP4 library is installed and processes MP4 files
Check the application version

For MPC-BE: right-click the executable, select Properties, check the Version tab. For other Bento4-using applications: check the application's 'About' or help documentation for version information.

Affected if The installed version predates the fix (commit 4341cb3) and no later security update has been applied
Verify MP4 file handling is enabled

Attempt to open a standard MP4 file in the application, or check application settings/preferences for media format support configurations.

Affected if MP4 parsing functionality is available and the application can process MP4 container files
Confirm the application processes untrusted MP4 input

Review whether the application is configured to automatically parse or preview MP4 files from external sources, network streams, or user-uploaded content.

Affected if The application can process MP4 files from untrusted or external sources without sanitization

The environment is affected if MPC-BE or any software using the Bento4 (AP4) library is present, processes MP4 files, and the version predates the fix for the NULL pointer dereference in AP4_AtomSampleTable::GetSample().

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update MPC-BE to the version containing commit 4341cb3 or later, which includes the fix for the NULL pointer dereference in the MP4 sample table parsing code.

Recommended fix Moderate confidence

Any MPC-BE version after commit 4341cb3

Obtain the fixed version of MPC-BE that includes commit 4341cb3 in the AP4_AtomSampleTable::GetSample() function
If using a package manager or pre-built binaries, wait for a new release that contains the fix
If building from source, checkout or download the code at commit 4341cb3 or later
Verify the fix resolves the null pointer dereference by testing with the crafted MP4 file that triggered the issue
Ensure any MP4 files from untrusted sources are scanned or rejected to prevent exploitation until the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing4.0 h
Review / QA2.0 h

10.0 hours of engineering $1,720

Get help mitigating

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 locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-36912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-36912 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-36912?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 10 hrs · Moderate

Typical engagement from $1,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-36912 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References