ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2025-12474

A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory.

Published Feb 11, 2026 · catalog updated Feb 11, 2026 · Google

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-12474. EPSS is 0.11%. Act only if a listed version of Google is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Low2.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.11%
Remediation
Vendor / distro source
Affected products
vendor Google libjxl 0.7 ≤0.11.1

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Google libjxl 0.7 ≤0.11.10.7 ≤0.11.1

How to fix CVE-2025-12474

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-12474. EPSS is 0.11%. Act only if a listed version of Google is installed.

Which versions are affected?

Compare what you have installed with Google libjxl 0.7 ≤0.11.1 0.7 ≤0.11.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 11, 2026 · EUVD

    Detected

    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.

  2. Feb 11, 2026 · EUVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2025-12474

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-12474

    30-day exploitation probability 0.11%

    first.org
  • EUVDVulnerability recordEUVD-2025-207023

    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 populat

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 3, 2026