CVE-2025-46407
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-46407 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 48th 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-46407, affects the BMPv3 Palette Decoding functionality in the SAIL Image Decoding Library version 0.9.8. The issue arises when loading a specially crafted BMP file, triggering an integer overflow that leads to a heap-based buffer overflow during palette reading. This flaw, classified under CWE-680 (Integer Overflow to Buffer Overflow), 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), highlighting its high severity due to potential for significant impact.
Exploitation requires an attacker to convince a user or application to load a malicious BMP file using the vulnerable library, typically through social engineering such as emailing or hosting a rigged image. No privileges are needed (PR:N), and it can be triggered over a network (AV:N) with low complexity (AC:L), though user interaction (UI:R) is required. Successful exploitation enables remote code execution, granting attackers high confidentiality, integrity, and availability impacts (C:H/I:H/A:H) within the context of the affected process.
The primary advisory is detailed in the Talos Intelligence report TALOS-2025-2215, available at https://talosintelligence.com/vulnerability_reports/TALOS-2025-2215. Security practitioners should consult this reference for recommended mitigations, such as updating to a patched version of the library if available or avoiding untrusted BMP files in applications leveraging SAIL.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-28036
Vulnerability Data
A memory corruption vulnerability exists in the BMPv3 Palette Decoding functionality of the SAIL Image Decoding Library v0.9.8. When loading a specially crafted .bmp file, an integer overflow can be made to occur which will cause a heap-based buffer to…
more
overflow when reading the palette from the image. These conditions can allow for 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.