PT-2025-40880 · Sanm+1 · Sanm+1

CVE-2025-59734 · Published 2025-08-21 · Updated 2026-06-26

Positive Technologies (AI Summary)

CVSS v4.0

8.7

High

Base vector

AV:A/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/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

Name of the Vulnerable Software and Affected Versions versions prior to 8.0

Description A crafted animation can trigger a use-after-free write during SANM decoding. This occurs when a STOR chunk is followed by an FOBJ chunk, and the frame has an invalid size. The code attempts to decode a frame object again, potentially reallocating a buffer while a GetByteContext object still holds a reference to the old buffer. This can lead to a use-after-free read when codecs use the GetByteContext object, and potentially corrupt allocator metadata by writing to freed data. The issue can be triggered by simply probing a file for the SANM format.

Recommendations Upgrade to version 8.0 or beyond.

Exploit

Fix

Use After Free

Weakness Enumeration

CWE-416

Related Identifiers

BDU:2025-12719

CVE-2025-59734

JLSEC-2026-647

Affected Products

Debian

Sanm

References · 20

• 🔥 https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/59xxx/CVE-2025-59734.json · Exploit
• https://osv.dev/vulnerability/CVE-2025-59734 · Vendor Advisory
• https://ubuntu.com/security/CVE-2025-59734 · Vendor Advisory
• https://osv.dev/vulnerability/DEBIAN-CVE-2025-59734 · Vendor Advisory
• https://security-tracker.debian.org/tracker/CVE-2025-59734 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2025-59734 · Security Note
• https://osv.dev/vulnerability/UBUNTU-CVE-2025-59734 · Vendor Advisory
• https://bdu.fstec.ru/vul/2025-12719 · Security Note
• https://cve.org/CVERecord?id=CVE-2025-59734 · Security Note
• https://osv.dev/vulnerability/JLSEC-2026-647 · Vendor Advisory
• https://issuetracker.google.com/issues/440183164 · Note
• https://b.corp.google.com/issues/440183164 · Note
• https://git.ffmpeg.org/ffmpeg.git · Note
• https://t.me/CVEtracker/34229 · Telegram Post
• https://twitter.com/CVEnew/status/1975120453728424393 · Twitter Post