CVE-2026-6385
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 flaw was found in FFmpeg. A remote attacker could exploit this vulnerability by providing a specially crafted MPEG-PS/VOB media file containing a malicious DVD subtitle stream. This vulnerability is caused by a signed integer overflow in the DVD subtitle parser's fragment reassembly bounds checks, leading to a heap out-of-bounds write. Successful exploitation can result in a denial of service (DoS) due to an application crash, and potentially lead to arbitrary code execution.
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 confidenceA signed integer overflow in FFmpeg's DVD subtitle parser's fragment reassembly bounds checks allows a remote attacker to trigger a heap out-of-bounds write via a specially crafted MPEG-PS/VOB file containing a malicious DVD subtitle stream, potentially leading to denial of service or arbitrary code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed FFmpeg versionRun 'ffmpeg -version' and note the version number in the outputAffected if The installed version contains the vulnerable DVD subtitle parser code (no specific safe version provided in CVE data)
-
Confirm DVD subtitle decoder is availableRun 'ffmpeg -codecs 2>&1 | grep -i dvdsub' or 'ffmpeg -decoders 2>&1 | grep -i dvdsub' to list DVD subtitle decodersAffected if The DVD subtitle decoder (dvdsub) is listed as available, indicating the vulnerable code path could be exercised
-
Check FFmpeg build configuration for subtitle supportRun 'ffmpeg -buildconf 2>&1' or 'ffprobe -version' to see which subtitle codecs are enabled in the buildAffected if DVD subtitle parsing is enabled in the build configuration
-
Verify ability to process MPEG-PS/VOB filesRun 'ffprobe -i <sample_vob_file> -show_streams 2>&1 | grep -i subtitle' on a test VOB file to confirm subtitle stream detection worksAffected if FFmpeg can parse and detect subtitle streams in VOB files, meaning the vulnerable parser is active
-
Inspect if subprocess or library usage is possibleCheck if any application uses libavformat/libavcodec to process VOB files by reviewing application logs or testing with a VOB file containing subtitlesAffected if An application or script can trigger FFmpeg to process DVD subtitles from VOB input
You are affected if your FFmpeg installation has DVD subtitle decoding enabled and processes MPEG-PS/VOB files from untrusted sources, regardless of version since no patched version range is specified in this CVE.
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.
From vendor dataUpdate FFmpeg to the latest patched version when available; until then, sanitize or reject MPEG-PS/VOB files from untrusted sources and disable DVD subtitle processing if not required.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6385 — 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-6385 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