Pixel-data disclosure via omitted patch population
Published Feb 11, 2026 · Updated Feb 11, 2026
Uninitialized memory use in Google libjxl 0.7 through 0.11.1 allows attackers to read stale pixel data via a crafted JPEG XL file. The low-memory render pipeline calculates incomplete per-stage spans for patches outside image bounds, skips populating those pixels, and later reads them. Processing a crafted image is required; the read is confined to allocated but uninitialized pixel memory, with no reported crash or code execution.
Summary
What happened
Uninitialized memory use in Google libjxl 0.7 through 0.11.1 allows attackers to read stale pixel data via a crafted JPEG XL file. The low-memory render pipeline calculates incomplete per-stage spans for patches outside image bounds, skips populating those pixels, and later reads them. Processing a crafted image is required; the read is confined to allocated but uninitialized pixel memory, with no reported crash or code execution.
The record
- CVE
- CVE-2025-12474
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Go standard library
- Product
- libjxl
- Classifications
- CWE-908, CAPEC-44, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.7 <=0.11.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo