cve.bz

CVE-2026-10758 esri lerc: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.5 highEPSS 0.3%

High (7.5) in esri lerc. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-10758 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-10758?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-10758?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-10758 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Esri Lerc0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hathummingbird:1liblerc, liblerc-devel, mingw32-liblerc and 1 more0:4.2.0-1.hum1RHSA-2026:45254
Azure Linux3liblercno fix listedAZL-105081

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A heap-based out-of-bounds write flaw was found in the LERC (Limited Error Raster Compression) library during image decoding. An integer overflow occurs when calculating memory allocations for attacker-controlled raster imagery, leading to heap memory corruption. In environments where an application ingests untrusted image data without prior validation, a remote attacker can exploit this condition to crash the host application process, resulting in a denial of service. Standard container boundaries and non-root execution typically confine the blast radius to single-process termination.

Red Hat's mitigation

Restrict the ingestion of LERC raster imagery to authenticated, trusted sources only. If untrusted input must be processed, isolate the parsing service inside an unprivileged, resource-constrained container or sandboxed worker process with automated restart limits.

ProductPackageStateAdvisory
Red Hat Hardened Imagesliblerc-main-4.2.0-1.hum1Fixed 2026-07-24RHSA-2026:45254
Red Hat Enterprise Linux 10liblercAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-10758.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON