# CVE-2026-5318: LibRaw JPEG DHT losslessjpeg.cpp initval out-of-bounds write

> Remote attackers can trigger an out-of-bounds write in LibRaw's JPEG parser, potentially leading to code execution or crashes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-5318, GHSA-8qw7-rqx6-9gqj, JLSEC-2026-1117, UBUNTU-CVE-2026-5318

## What is CVE-2026-5318?

CVE-2026-5318 is a medium-severity memory corruption vulnerability in Libraw Libraw, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in LibRaw up to 0.22.0. This impacts the function HuffTable::initval of the file src/decompressors/losslessjpeg.cpp of the component JPEG DHT Parser. This manipulation of the argument bits[] causes out-of-bounds write. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 0.22.1 will fix this issue. Patch name: a6734e867b19d75367c05f872ac26322464e3995. It is advisable to upgrade the affected component.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Libraw Libraw.

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

Upgrade to a fixed version.

## Is CVE-2026-5318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5318 exists.

## 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-2026-21413](https://insights.sbomify.com/CVE-2026-21413/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5318 is a medium-severity memory corruption vulnerability in Libraw Libraw, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5318 exists.

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

## Sources

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

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