# CVE-2026-21413: Memory corruption in LibRaw

> A heap-based buffer overflow in LibRaw allows attackers to execute arbitrary code or cause denial of service via a malicious JPEG file.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 7 Apr 2026
- **Updated:** 13 Oct 2026
- **Also known as:** AZL-82955, CLSA-2026-1777889999, CLSA-2026-1777941038, DEBIAN-CVE-2026-21413, ECHO-602f-3dc6-d1d6, GHSA-g53g-r75r-95g5, JLSEC-2026-1115, RHSA-2026:13860, RHSA-2026:13868, UBUNTU-CVE-2026-21413

## What is CVE-2026-21413?

CVE-2026-21413 is a critical memory corruption vulnerability in Libraw Libraw, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-based buffer overflow vulnerability exists in the lossless_jpeg_load_raw functionality of LibRaw Commit 0b56545 and Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-129 (Improper Validation of Array Index)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `LibRaw` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:0.20.2-6.el9_0 |
| `LibRaw-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:0.20.2-6.el9_0 |
| `LibRaw-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:0.20.2-6.el9_0 |
| `LibRaw-samples-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:0.20.2-6.el9_0 |
| `LibRaw` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:0.20.2-6.el9_2 |
| `LibRaw-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:0.20.2-6.el9_2 |
| `LibRaw-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:0.20.2-6.el9_2 |
| `LibRaw-samples-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:0.20.2-6.el9_2 |

Products: Libraw Libraw.

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

Upgrade to a fixed version.

## Is CVE-2026-21413 being exploited?

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

## Other vulnerabilities in Libraw Libraw

- [CVE-2026-20889](https://insights.sbomify.com/CVE-2026-20889/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2026-20911](https://insights.sbomify.com/CVE-2026-20911/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2015-8366](https://insights.sbomify.com/CVE-2015-8366/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-8367](https://insights.sbomify.com/CVE-2015-8367/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14265](https://insights.sbomify.com/CVE-2017-14265/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21413 is a critical memory corruption vulnerability in Libraw Libraw, published on 7 Apr 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-21413 in the wild and no public exploit code.

Affected product: Libraw Libraw. 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-21413/ (Markdown: https://insights.sbomify.com/CVE-2026-21413/index.md)
```

## Sources

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

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