CVE-2025-52456
Sail 0.9.8
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-52456 is a high-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Sail Sail. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A memory corruption vulnerability, designated CVE-2025-52456, affects the WebP Image Decoding functionality in the SAIL Image Decoding Library version 0.9.8. The issue arises when processing a specially crafted .webp animation, triggering an integer overflow during stride calculation for decoding. This overflow subsequently causes a heap-based buffer overflow, potentially enabling remote code execution. The vulnerability is classified under CWE-680 (Integer Overflow or Wraparound) and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
An unauthenticated attacker over the network can exploit this vulnerability with low complexity by convincing a user to load the malicious .webp file through an application that uses the affected SAIL library. User interaction is required, such as opening the file in a supporting image viewer or application. Successful exploitation could result in arbitrary code execution with the privileges of the affected process, compromising confidentiality, integrity, and availability with high impact.
For mitigation details, security practitioners should consult the primary advisory from Talos Intelligence at https://talosintelligence.com/vulnerability_reports/TALOS-2025-2224. No specific patches are detailed in the available information.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-25737
Vulnerability Data
A memory corruption vulnerability exists in the WebP Image Decoding functionality of the SAIL Image Decoding Library v0.9.8. When loading a specially crafted .webp animation an integer overflow can be made to occur when calculating the stride for decoding. Afterwards,…
more
this will cause a heap-based buffer to overflow when decoding the image which can lead to remote code execution. An attacker will need to convince the library to read a file to trigger this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.
Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.
Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.
Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect integer-overflow-to-buffer-overflow conditions during development.
Secure development life cycle mandates practices that can catch integer overflows before deployment.
Application security requirements can specify safe integer handling and bounds checking.
Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.
Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.