CVE-2025-12474
Uninitialized Memory Read in libjxl Decoder via Crafted File
Publication date: 2026-02-11
Last updated on: 2026-04-24
Assigner: Google Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| libjxl_project | libjxl | From 0.7.0 (inc) to 0.11.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-908 | The product uses or accesses a resource that has not been initialized. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the libjxl image decoding library where a specially-crafted file can cause the decoder to read pixel data from uninitialized but allocated memory.
The issue arises because the decoder references areas outside the image bounds in subsequent patches, and due to an incorrect optimization, it fails to populate those areas properly.
How can this vulnerability impact me? :
The impact of this vulnerability is that the libjxl decoder may read uninitialized memory, which could potentially lead to information disclosure or cause instability in applications using the library.
However, the CVSS base score is low (2.3), indicating that the vulnerability has limited impact and requires high attack complexity with user interaction.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2025-12474, you should update the libjxl library to include the fix implemented in Pull Request #4495.
This fix improves the low memory rendering pipeline by correcting parameter calculations and refactoring code to enhance stability and correctness under low memory conditions, thereby preventing the decoder from reading uninitialized memory.
Ensure that your libjxl version includes this patch merged on October 29, 2025, to protect against this issue.