CVE-2026-93019
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-93019 is a critical-severity Unsigned to Signed Conversion Error (CWE-196) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-82927
Vulnerability Data
Imager versions before 1.036 for Perl exit the process reading a TGA with a colour map length of 32768 or more in tga_palette_read. The reader unpacks the two-byte colour map length into a signed short, so a length of 32768…
more
or more becomes negative. tga_palette_read() casts that value to size_t and asks mymalloc() for a size near SIZE_MAX. The allocation fails and Imager's allocator calls exit(3). Reading an attacker-supplied file through Imager->read() triggers an uncatchable exit.
- 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 evaluation can discover unsigned-to-signed conversion errors through targeted test cases or analysis.
Requiring documented development standards and tools can mandate safe integer handling and prohibit unsafe casts.
Security engineering principles can include explicit rules for safe type conversion and arithmetic operations.
Resource quotas and priority allocation limit the system-wide impact of an oversized request.
Input validation directly rejects or bounds untrusted size values before any allocation occurs.
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 (reviews, static analysis, safe integer handling) directly prevent unsigned-to-signed conversion errors during development.
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.
Secure development lifecycle mandates practices that can catch or prevent unsafe type conversions.
Application security requirements can specify safe handling of numeric types and bounds checking.
Secure architecture principles include choosing appropriate data types and avoiding implicit conversions.
Secure coding standards directly address avoiding unsafe casts from unsigned to signed integers.
Security testing can detect integer conversion errors through static analysis and fuzzing.