Skip to content
Fencer Vulns
high 7.5

CVE-2026-10758 json

Esri Lerc has a security vulnerability

published 2026-09-25 44 d ago modified 2026-09-30 39 d ago also EUVD-2026-87360

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

Esri LERC is an open-source image or raster format which supports rapid encoding and decoding for any pixel type. A Heap based Out-of-Bounds Write via Integer Overflow in LERC versions 4.1.0 and earlier may allow a remote, unauthenticated attacker who can pass specifically crafted attacker controlled imagery to an application that uses LERC to crash the application, leading to a denial of service.

Patch / fix

  • liblerc hummingbird 1 4.2.0-1.hum1
  • mingw32-liblerc hummingbird 1 4.2.0-1.hum1
  • mingw64-liblerc hummingbird 1 4.2.0-1.hum1

red hat advisories RHSA-2026:45254

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-10758 updated cvss 7.5

lerc: lerc: Denial of Service via heap-based out-of-bounds write

  • Red Hat Enterprise Linux 10 liblerc
    affected: workaround, no fix available
  • Red Hat Hardened Images liblerc 4.2.0-1.hum1, mingw32-liblerc 4.2.0-1.hum1, mingw64-liblerc 4.2.0-1.hum1
    fixed: vendor fix RHSA-2026:45254

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
43 d ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Esri Lerc

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.