# CVE-2026-40340: libgphoto2 has OOB read in ptp_unpack_OI() in ptp-pack.c via malicious PTP ObjectInfo response

> An out-of-bounds read in libgphoto2 allows attackers to cause denial of service or disclose information via a malicious PTP response.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** AZL-83030, DEBIAN-CVE-2026-40340, GHSA-xfw3-xvjp-5wcv, UBUNTU-CVE-2026-40340

## What is CVE-2026-40340?

CVE-2026-40340 is a medium-severity memory corruption vulnerability in libgphoto2, published on 17 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

libgphoto2 is a camera access and control library. Versions up to and including 2.5.33 have an out-of-bounds read vulnerability in `ptp_unpack_OI()` in `camlibs/ptp2/ptp-pack.c` (lines 530–563). The function validates `len < PTP_oi_SequenceNumber` (i.e., len < 48) but subsequently accesses offsets 48–56, up to 9 bytes beyond the validated boundary, via the Samsung Galaxy 64-bit objectsize detection heuristic. Commit 7c7f515bc88c3d0c4098ac965d313518e0ccbe33 fixes the issue.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-40340 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40340 is a medium-severity memory corruption vulnerability in libgphoto2, published on 17 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40340 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-40340/ (Markdown: https://insights.sbomify.com/CVE-2026-40340/index.md)
```

## Sources

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

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