Skip to main content
No exploitation reportedFix available

CVE-2026-1837

No exploitation reported by the sources we read.

  • Published2026-02-11
  • WeaknessCWE-770 · CWE-787 · CWE-805

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory. Soon after that data from another uninitialized unallocated region is copied to pixel data. This can be done by requesting color transformation of grayscale images to another grayscale color space. Buffers allocated for 1-float-per-pixel are used as if they are allocated for 3-float-per-pixel. That happens only if LCMS2 is used as CMS engine. There is another CMS engine available (selected by build flags).

Timeline

dates in UTC
  1. 2026-02-1116:16CVE publishedNVD

Versions per branch

NVD
Libjxl project libjxl
BranchAffectedFixed in
0.x≥ 0.9.0, ≤ 0.11.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Google, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google libjxlother versions: not affected
    Affected
    • ≥ 0.9, ≤ 0.11.1no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-11

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • jpeg-xlUbuntu:25.10all versions · fixed in 0.11.1-6ubuntu1.1
  • jpeg-xlDebian:14all versions · fixed in 0.11.2-0.1
  • jpeg-xlDebian:13all versions · fixed in 0.11.2-0.1~deb13u1
  • libjxlSUSE:Linux Enterprise Server for SAP applications 16.0all versions · fixed in 0.11.2-160000.1.1
  • libjxlSUSE:Linux Enterprise Server 16.0all versions · fixed in 0.11.2-160000.1.1
  • libjxlSUSE:Linux Enterprise Module for Package Hub 15 SP7all versions · fixed in 0.10.3-150700.4.6.1
  • libjxlopenSUSE:Tumbleweedall versions · fixed in 0.11.2-1.1
  • libjxlopenSUSE:Leap 16.0all versions · fixed in 0.11.2-160000.1.1

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-1837 Red Hat Product Security

    libjxl: libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2026-02-13
  • CNACVSS 4.08.7known since 2026-10-23
  • CNACVSS 3.18.8known since 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-787, CWE-805known since 2026-10-23
  • NVDweakness (CWE)CWE-770read 2026-10-23
  • FIRST EPSSEPSS score0.3 %2026-11-18
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-02-11
Last Modified
2026-07-15
NVD status
Modified
GitHub Advisory
GHSA-76gx-97cq-65f5

Frequently asked questions

What is CVE-2026-1837?

A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory. Soon after that data from another uninitialized unallocated region is copied to pixel data. This can be done by requesting color transformation of grayscale images to another grayscale color space. Buffers allocated for 1-float-per-pixel are used as if they are allocated for 3-float-per-pixel. That happens only if LCMS2 is used as CMS engine. There is another CMS engine available (selected by build flags).

Is CVE-2026-1837 actively exploited?

Active exploitation of CVE-2026-1837 has not been confirmed. Its EPSS score was 0.3% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-1837?

CVE-2026-1837 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running libjxl? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record