MEDIUM 5.5

CVE-2026-36907: Bento4 Stack Overflow in MP4 Parsing – DoS Vulnerability

A stack overflow vulnerability exists in Bento4, a multimedia framework used for MP4 file processing. The flaw resides in how the AP4_StsdAtom component handles crafted MP4 files, allowing an attacker to trigger a denial-of-service condition by causing the application to crash. The vulnerability requires local access and user interaction (opening a malicious file), but does not allow data theft or system modification—only service disruption.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-121
Affected products
0 configuration(s)
Published / Modified
2026-06-26 / 2026-06-29

NVD description (verbatim)

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.

4 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-36907 is a stack buffer overflow (CWE-121) in the AP4_StsdAtom::AP4_StsdAtom constructor within axiomatic-systems Bento4 prior to version 1.8.9. The vulnerability is triggered during MP4 file parsing when the stsd (sample description) atom is malformed. The overflow can cause memory corruption on the stack, leading to application crash or potential control flow hijacking. The CVSS 3.1 score of 5.5 (MEDIUM) reflects local attack surface, no privileges required, user interaction necessary, and availability impact only.

Business impact

Organizations using Bento4 for media processing, transcoding pipelines, or embedded MP4 handling face availability disruption if an attacker supplies a weaponized MP4 file. Automated workflows (batch video processing, media validation services) are at higher risk since they may process untrusted files without human review. This is not a confidentiality or integrity threat, but repeated crashes can degrade service reliability and increase operational support costs.

Affected systems

Bento4 versions prior to 1.8.9 are affected. Bento4 is used in media players, streaming platforms, video editing tools, and backend media processing services. Any deployment or product incorporating the vulnerable Bento4 library is at risk if it processes MP4 files from untrusted sources. The vendor product list was not populated in the ground-truth source, so operators should audit their software bill of materials (SBOM) for Bento4 presence and version.

Exploitability

Exploitation requires local file system access and user or process interaction to open a crafted MP4 file. No network vector, no authentication bypass, and no remote execution. The attack is straightforward—a malicious MP4 file designed to overflow the stsd atom parser—but the impact is limited to denial of service. This is not currently tracked on the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating no widespread active exploitation has been publicly disclosed.

Remediation

Upgrade Bento4 to version 1.8.9 or later. Organizations should verify their upgrade path with the vendor, as dependency chains and build systems may require coordination. Interim mitigations include restricting MP4 file processing to trusted sources, implementing file validation before parsing, and running media processing in isolated or sandboxed environments to limit crash impact.

Patch guidance

Apply Bento4 version 1.8.9 or later. Verify the patch availability through the axiomatic-systems official release channels and test in a staging environment before production rollout. If Bento4 is embedded in a larger product, confirm that the product's maintainer has released an update incorporating the patched library. Check release notes to ensure no breaking changes affect your media pipeline.

Detection guidance

Monitor for crash logs or abnormal termination of Bento4-based processes when processing MP4 files. Implement file integrity and reputation scanning for uploaded or ingested MP4s. If feasible, enable stack canaries or memory sanitizers (ASAN, Valgrind) during development to catch buffer overflows early. Log all MP4 file processing errors and correlate spikes in crashes with suspicious file sources.

Why prioritize this

While the CVSS score is MEDIUM, prioritization depends on your usage pattern. If Bento4 is exposed in an automated, internet-facing media processing service, upgrade immediately. If Bento4 is used only in offline, trusted workflows, patching can be scheduled in a standard maintenance window. The lack of KEV designation and network exploitability means this is not a critical emergency, but should not be indefinitely delayed.

Risk score, explained

CVSS 5.5 reflects: (1) local attack vector only, (2) low attack complexity, (3) no privilege escalation needed, (4) user interaction required (file must be opened/processed), (5) isolated scope (no lateral spread), (6) high availability impact (crash). The score does not account for prevalence of Bento4 in your infrastructure or the sensitivity of your media processing pipeline—those factors should inform your internal risk rating.

Frequently asked questions

Is this vulnerability remotely exploitable?

No. The attack vector is local (AV:L), meaning an attacker must either have file system access or convince a user to process a malicious MP4 file. There is no network-based exploitation path.

Can an attacker steal data or modify files using this vulnerability?

No. The vulnerability only causes denial of service (application crash). The CVSS vector shows C:N (no confidentiality impact) and I:N (no integrity impact). Data exfiltration and file tampering are not possible.

Is there a public exploit or proof-of-concept for this vulnerability?

CVE-2026-36907 is not listed in CISA's Known Exploited Vulnerabilities catalog, indicating no public exploit or active exploitation campaign has been widely disclosed. However, a proof-of-concept MP4 file crafted to trigger the stack overflow is likely trivial to construct for anyone with knowledge of the MP4 file format.

What if we cannot upgrade Bento4 immediately due to compatibility concerns?

Implement compensating controls: restrict MP4 input to trusted sources, run media processing in containers or sandboxed environments, deploy file scanning/validation before Bento4 processes files, and monitor for unexpected crashes. These do not fix the underlying bug but reduce the likelihood and impact of exploitation.

This analysis is provided for informational purposes and based on publicly available vulnerability data as of the publication date. No exploit code or weaponized proof-of-concept is provided. Patch versions and remediation steps should be verified against official vendor advisories. SEC.co makes no warranty regarding the completeness or accuracy of this analysis. Organizations must conduct their own risk assessment and testing before applying patches or implementing mitigations in production environments. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).