CVE-2025-22920
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 heap buffer overflow vulnerability in FFmpeg before commit 4bf784c allows attackers to trigger a memory corruption via supplying a crafted media file in avformat when processing tile grid group streams. This can lead to a Denial of Service (DoS).
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 confidenceHeap buffer overflow vulnerability in FFmpeg's avformat component when processing tile grid group streams (commonly used in JPEG2000 and similar tiled image/video formats). Attackers can trigger memory corruption by supplying a crafted media file, leading to potential 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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' or 'ffmpeg -buildconf' to display the version string and build configurationAffected if The version predates the fix (commit 4bf784c) and you cannot confirm the vulnerability is patched
-
Confirm avformat component is in useCheck if FFmpeg is being used to demux or parse media files; verify the avformat library is loaded by running 'ffmpeg -formats 2>/dev/null | head -20'Affected if avformat handles the file parsing and is involved in processing the affected tile grid streams
-
Determine if processing JPEG2000 or tiled image/video formatsInspect your media processing pipeline for files with extensions such as .jp2, .j2k, .mj2, or other JPEG2000-based formats; review logs or input files for tile-based encodingAffected if The vulnerability is triggered specifically when processing tile grid group streams commonly found in JPEG2000 and similar tiled formats
-
Inspect file processing inputs for untrusted mediaReview any media files submitted to FFmpeg for processing, particularly from untrusted or external sources, looking for crafted files targeting tile grid parsingAffected if A crafted media file with malicious tile grid group data is processed by the vulnerable avformat code path
You are affected if you run an unpatched FFmpeg version (prior to the fix commit 4bf784c) and process JPEG2000 or other tiled image/video formats from untrusted sources using avformat.
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 a version that includes commit 4bf784c or later. If immediate patching is not feasible, implement input validation on media files before processing and consider sandboxing FFmpeg processing to limit impact of potential exploitation.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22920 — 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-2025-22920 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