dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-59730

MEDIUM · 5.7 CVSS v4.0 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated

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
When decoding a frame for a SANM file (ANIM v0 variant), the decoded data can be larger than the buffer allocated for it. Frames encoded with codec 48 can specify their resolution (width x height). A buffer of appropriate size is allocated depending on the resolution. This codec can encode the frame contents using a run-length encoding algorithm. There are no checks that the decoded frame fits in the allocated buffer, leading to a heap-buffer-overflow. process_frame_obj initializes the buffers based on the frame resolution: We recommend upgrading to version 8.0 or beyond.

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 · high confidence

A heap-buffer-overflow vulnerability exists in the SANM/ANIM file decoder when processing codec 48 frames. The codec allows specifying arbitrary frame resolution and uses run-length encoding without validating that decoded data fits within the pre-allocated buffer, leading to out-of-bounds memory writes.

MitigationUpgrade to version 8.0 or later as recommended. Until then, avoid processing untrusted SANM/ANIM files with codec 48.

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
Adjacent
Complexity
High
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 SANM/ANIM decoder software
    Locate all media processing applications or libraries capable of decoding SANM/ANIM files in your environment. Check installed programs for components that handle .anim, .sanm, or similar animation file formats.
    Affected if A program or library with SANM/ANIM decoding capability is present and the version is unknown or below 8.0
  2. Determine decoder version
    For each identified SANM/ANIM decoder, run its version command (e.g., --version, -v, or check file properties). Compare against the fixed version 8.0.
    Affected if The installed version is below 8.0 or cannot be determined
  3. Verify codec 48 support is present
    Check decoder documentation, help output, or binary capabilities for support of codec 48 (also called SANM codec 48 orAnim codec 48). This is typically listed in supported codec enumerations.
    Affected if Codec 48 is listed as a supported format
  4. Inspect for recent ANIM file processing
    Review application logs, recently opened files, or process history for any .anim, .sanm, or animation file types processed by the decoder.
    Affected if The decoder has processed SANM/ANIM files, especially with unknown or untrusted origin
  5. Check for heap-related crashes
    Review system/application crash logs (core dumps, event logs, crash reports) for heap-buffer-overflow errors occurring in the SANM/ANIM decoder component.
    Affected if Heap corruption or buffer overflow crashes are logged in the decoder code path

You are affected if you have a SANM/ANIM decoder version below 8.0 that supports codec 48 and have processed or may process untrusted ANIM/SANM files.

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 to version 8.0 or later as recommended. Until then, avoid processing untrusted SANM/ANIM files with codec 48.

Recommended fix High confidence

FFmpeg 8.0 or later

  1. 1. Identify the current FFmpeg/libavformat version installed on the system using: ffmpeg -version or avconv -version
  2. 2. Check if the current version is below 8.0
  3. 3. Upgrade FFmpeg to version 8.0 or later by obtaining a build from your distribution's package manager (e.g., apt-get update && apt-get install ffmpeg, yum install ffmpeg, or brew install ffmpeg)
  4. 4. Alternatively, compile FFmpeg from source by downloading version 8.0 or later from https://ffmpeg.org/download.html
  5. 5. Verify the upgrade was successful by running: ffmpeg -version and confirming the version number is 8.0 or higher
  6. 6. Test that applications using libavformat can now properly handle SANM/ANIM files without crashes
Caveat Major version upgrades in FFmpeg may introduce API changes that require recompilation of dependent applications; review the FFmpeg 8.0 release notes for any breaking changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59730 — 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-2025-59730 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