dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-36907

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges 8 weeks old

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 · unedited
A stack overflow in the AP4_StsdAtom::AP4_StsdAtom component of axiomatic-systems Bento4 before v1.8.9allows 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 confidence

A stack overflow vulnerability exists in the AP4_StsdAtom::AP4_StsdAtom component of Bento4, a C++ MP4 parsing library. The vulnerability is triggered when parsing a specially crafted MP4 file with a malformed sample description (stsd) atom, leading to stack corruption and denial of service.

MitigationUpgrade Bento4 to version 1.8.9 or later to resolve the stack overflow vulnerability. Additionally, implement file type validation and consider sandboxing MP4 parsing operations to limit the impact of malicious files.

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 checks

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

  1. Identify if Bento4 library is in use
    Search for Bento4 library files (libBento4.so, libBento4.a, Bento4.dll) or header files (Ap4*.h) in the system or application dependencies. Check application manifests or build configurations for Bento4 linkage.
    Affected if Bento4 library or its usage cannot be found in the environment (not vulnerable if Bento4 is not present).
  2. Determine installed Bento4 version
    Check the version string in the library binary, header file (often in AP4_Version.h or similar), or query the library at runtime if it exposes a version API. Look for version markers like '1.8.x' in source files or binary metadata.
    Affected if Version cannot be determined or is earlier than 1.8.9.
  3. Verify MP4 parsing with stsd atom processing is enabled
    Identify if the application or service uses AP4_StsdAtom parsing functionality. Review code that handles MP4 file parsing, particularly the sample description (stsd) atom processing path. Check if untrusted MP4 files are accepted as input.
    Affected if The environment parses MP4 files and processes the stsd atom, and processes files from untrusted sources.
  4. Compare version to affected range
    If Bento4 version is identified, compare it against the affected range: versions prior to 1.8.9. Any version 1.8.8, 1.8.0, 1.7.x, 1.6.x or earlier are within the vulnerable range.
    Affected if Installed Bento4 version is 1.8.8 or earlier.

The environment is affected if Bento4 version 1.8.8 or earlier is in use and the application parses MP4 files containing the stsd atom from potentially untrusted sources.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Bento4 to version 1.8.9 or later to resolve the stack overflow vulnerability. Additionally, implement file type validation and consider sandboxing MP4 parsing operations to limit the impact of malicious files.

Recommended fix High confidence

Bento4 v1.8.9 or later

  1. Upgrade Bento4 library to version 1.8.9 or later
  2. If using a package manager, update the Bento4 dependency to the latest available version
  3. If building from source, clone the repository and checkout version v1.8.9 or the latest release tag
  4. Rebuild and redeploy any applications using Bento4
  5. Test with the affected MP4 parsing functionality to verify the vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36907 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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