# CVE-2026-10758: Esri Lerc has a security vulnerability

> A remote attacker can cause a denial of service by sending crafted imagery to applications using the Esri Lerc library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** AZL-105081, GHSA-cw29-mw7w-pj37, GHSA-gfc2-qmh7-jf3x, RHSA-2026:45254

## What is CVE-2026-10758?

CVE-2026-10758 is a high-severity vulnerability in Esri Lerc, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-10758?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `liblerc` | Red Hat:hummingbird:1 | All versions | 0:4.2.0-1.hum1 |
| `liblerc-devel` | Red Hat:hummingbird:1 | All versions | 0:4.2.0-1.hum1 |
| `mingw32-liblerc` | Red Hat:hummingbird:1 | All versions | 0:4.2.0-1.hum1 |
| `mingw64-liblerc` | Red Hat:hummingbird:1 | All versions | 0:4.2.0-1.hum1 |

## How do I fix CVE-2026-10758?

Upgrade to a fixed version.

## Is CVE-2026-10758 being exploited?

There is no known exploitation of CVE-2026-10758 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10758 and fix it if it is affected.

What it is: CVE-2026-10758 is a high-severity vulnerability in Esri Lerc, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10758 in the wild and no public exploit code.

Affected product: Esri Lerc. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10758/ (Markdown: https://insights.sbomify.com/CVE-2026-10758/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10758
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10758
- OSV: https://osv.dev/vulnerability/CVE-2026-10758

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10758/
Summaries are generated and may contain mistakes; the official description above is the record.