# CVE-2026-120452: libgphoto2 through 2.5.34 Heap Out-of-Bounds Read/Write via jl2005c Thumbnail Conversion


- **Severity:** Medium 5.2 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** AZL-112523, DEBIAN-CVE-2026-120452, GHSA-4cvw-qwj9-xjc2, UBUNTU-CVE-2026-120452

## What is CVE-2026-120452?

CVE-2026-120452 is a medium-severity vulnerability in libgphoto2, published on 2 Nov 2026. 

### Official description

libgphoto2 through 2.5.34 contains a heap out-of-bounds read and write vulnerability in jl2005bcd_decompress() that allows malicious USB cameras to corrupt heap memory via oversized thumbnail processing. Attackers can supply small allocation-table values and a thumbnail header byte so in-place byte-swapping exceeds the buffer by about 30 KB, leaking heap contents in preview images.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120452 is a medium-severity vulnerability in libgphoto2, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120452 in the wild and no public exploit code.

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

## Sources

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

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