# CVE-2026-120451: libgphoto2 through 2.5.34 Buffer Overflow via jl2005c Camera Driver


- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** AZL-112520, DEBIAN-CVE-2026-120451, GHSA-7rfg-j54g-6xm2, UBUNTU-CVE-2026-120451

## What is CVE-2026-120451?

CVE-2026-120451 is a high-severity vulnerability in libgphoto2, published on 2 Nov 2026. 

### Official description

libgphoto2 through 2.5.34 contains stack-based and heap-based buffer overflow vulnerabilities in jl2005c_init() that allow malicious USB devices to corrupt memory by supplying an unbounded allocation table entry count. Attackers can connect a spoofed Jeilin JL2005B/C/D camera reporting 1022 or more entries to overwrite the saved return address and heap data, potentially achieving code execution.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-120451 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120451 is a high-severity vulnerability in libgphoto2, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120451 exists.

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

## Sources

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

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