CVE-2025-12474: A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memo

Routine

MEDIUM 4.4UPGRADE

CVE-2025-12474 is a medium-severity flaw (CVSS 4.4) affecting libjxl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.4 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-908
Published	2026-02-11
Last modified	2026-06-17

Publisher (CNA): Google Inc. · Vendor: libjxl project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-11 16:15 UTCPublished CVE record published
2026-06-17 08:32 UTCUpdated Record last modified

libjxl project libjxl UPGRADE

Affected: >= 0.7.0 and <= 0.11.1

Fixed in: newer than 0.11.1

Safe to downgrade to: a release before 0.7.0

1. Check installed version

apt-cache policy libjxl || rpm -q libjxl || libjxl --version

2. UPGRADE to newer than 0.11.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libjxl

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libjxl

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.7.0 (Debian / Ubuntu)

apt-cache madison libjxl sudo apt install libjxl=<VERSION_BEFORE_0.7.0> sudo apt-mark hold libjxl

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libjxl sudo dnf downgrade libjxl-<VERSION_BEFORE_0.7.0> sudo dnf versionlock add libjxl

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-12474?

libjxl: upgrade to newer than 0.11.1. Exact commands for each OS are on this page.

Is CVE-2025-12474 being exploited?

CVE-2025-12474 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-12474 affect?

CVE-2025-12474 affects libjxl. Severity is medium (CVSS 4.4). 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 optimi

How urgent is CVE-2025-12474?

Priority 16/100. No elevated risk signals yet.

Related CVEs

CVE-2026-1837 HIGH 7.5 UPGRADE A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory
CVE-2024-11498 HIGH 7.5 UPGRADE There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to u
CVE-2024-11403 CRITICAL 9.8 UPGRADE There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33

References

← Back to latest CVEs