CVE-2025-12474

libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling

MEDIUM
4.4
CVSS Score
Published: February 11, 2026 at 03:27 PM UTC
Updated: June 17, 2026 at 08:32 AM UTC
1 product affected across 1 vendorLibjxl

Using libjxl by Google?

Get instant alerts when new vulnerabilities affect libjxl - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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 omit populating those areas.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.7 ≤ v ≤ 0.11.10.7.0 ≤ v ≤ 0.11.10.7

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Issue TrackingPatch
Source: cverecord
https://github.com/libjxl/libjxl/pull/4495

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card