Security Resilience

CVE-2025-12474

Libjxl Project Libjxl 0.7.0 – 0.11.1

Published
11 February 2026
Modified
24 April 2026
Patch / advisory
CVSS Score v4 2.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/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
EPSS Score 0.0011 1th percentile
Risk Priority 15 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-12474 is a low-severity Use of Uninitialized Resource (CWE-908) vulnerability in Libjxl Project Libjxl. Its CVSS base score is 2.3 (Low).

Operationally, ranked at the 1th 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

Vulnerability Data

A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory. This can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to…

more

omit populating those areas.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-1837Same product: Libjxl Project Libjxl
CVE-2024-11403Same product: Libjxl Project Libjxl
CVE-2023-35790Same product: Libjxl Project Libjxl
CVE-2023-0645Same product: Libjxl Project Libjxl
CVE-2024-11498Same product: Libjxl Project Libjxl
CVE-2025-29829Shared CWE-908
CVE-2024-26209Shared CWE-908
CVE-2023-29367Shared CWE-908
CVE-2023-32213Shared CWE-908
CVE-2023-52577Shared CWE-908

Affected Assets

libjxl project
libjxl
0.7.0 — 0.11.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.

Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.

Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.

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.

PR.PS-06 mostly match
blocks

Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.

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.

finds

Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.

prevents

Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.

References