CVE-2026-1837

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-02-11. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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).

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

February 11, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
Patch available. Sources: redhat.
redhat

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1837.json
generic

Crash in CMS when requesting grayscale colorspace · Issue #4549 · libjxl/libjxl · GitHub

https://github.com/libjxl/libjxl/issues/4549
redhat

2438974 – (CVE-2026-1837) CVE-2026-1837 libjxl: libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2

https://bugzilla.redhat.com/show_bug.cgi?id=2438974
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-1837

Vendor Advisories for CVE-2026-1837(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibjxl0.11 (0.11.1-6ubuntu1.1) @ questing2026-06-12ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jpeg-xl0.11.1-4, 0.11.1-5, 0.11.1-60.11.2-0.1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jpeg-xl0.11.1-4, 0.11.1-5, 0.11.1-6, 0.11.2-0.1~deb13u1, 0.11.2-0.1~deb13u20.11.2-0.1—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 203 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:14 UTCEPSS rescore
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 19:04 UTCOSV refresh
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 22:39 UTCVendor advisory
  7. 2026-08-14 22:39 UTCGHSA enrichment
  8. 2026-08-14 10:23 UTCEG score recompute
  9. 2026-08-14 10:23 UTCVendor advisory
  10. 2026-08-14 10:23 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 02:38 UTCEG score recompute
  13. 2026-08-13 02:38 UTCVendor advisory
  14. 2026-08-13 02:38 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 09:16 UTCEG score recompute
  18. 2026-08-11 09:16 UTCVendor advisory
  19. 2026-08-11 09:16 UTCGHSA enrichment
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 03:11 UTCVendor advisory
  22. 2026-08-10 03:11 UTCGHSA enrichment
  23. 2026-08-09 15:04 UTCEG score recompute
  24. 2026-08-09 15:04 UTCVendor advisory
  25. 2026-08-09 15:04 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-08 10:18 UTCVendor advisory
  29. 2026-08-08 10:18 UTCGHSA enrichment
  30. 2026-08-07 22:12 UTCEG score recompute
  31. 2026-08-07 22:12 UTCVendor advisory
  32. 2026-08-07 22:12 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 04:01 UTCEG score recompute
  35. 2026-08-06 04:01 UTCVendor advisory
  36. 2026-08-06 04:01 UTCGHSA enrichment
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 10:38 UTCEPSS rescore
  40. 2026-08-03 10:35 UTCEPSS rescore
  41. 2026-08-02 20:50 UTCEG score recompute
  42. 2026-08-02 20:50 UTCVendor advisory
  43. 2026-08-02 20:50 UTCGHSA enrichment
  44. 2026-08-02 02:26 UTCEPSS rescore
  45. 2026-08-01 04:15 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-27 14:13 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-25 14:17 UTCEPSS rescore
  51. 2026-07-25 14:17 UTCEPSS rescore
  52. 2026-07-24 14:17 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 03:06 UTCEG score recompute
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 14:31 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-19 02:28 UTCEPSS rescore
  64. 2026-07-18 10:04 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-17 16:29 UTCOSV refresh
  67. 2026-07-16 17:03 UTCEPSS rescore
  68. 2026-07-16 17:03 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 7.5
  72. 2026-07-15 02:06 UTCMITRE cvelistV5CVSS v3 → 8.8
  73. 2026-07-15 02:00 UTCEPSS rescore
  74. 2026-07-15 02:00 UTCEPSS rescore
  75. 2026-07-13 22:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-1837?
CVE-2026-1837 is a high vulnerability published on February 11, 2026. 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…
When was CVE-2026-1837 disclosed?
CVE-2026-1837 was first published in the National Vulnerability Database on February 11, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1837 actively exploited?
CVE-2026-1837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.6% of all scored CVEs.
What is the CVSS score of CVE-2026-1837?
CVE-2026-1837 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-1837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1837, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1837

Explore →

Is Your Infrastructure Affected by CVE-2026-1837?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs