Skip to main content
VulnerabilityPublished Updated

CVE-2026-40341: gphoto libgphoto2 · Buffer Over-read

Affects gphoto libgphoto2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.5 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
gphotolibgphoto2Affected
  • <=2.5.33
Fixed in–
GitHubgphoto/libgphoto2pkg:github/gphoto/libgphoto2Other threatsAffected
  • <=2.5.33
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch addressing this vulnerability exists in the identified commit, but no official vendor advisory or released patch is currently confirmed. Users should monitor the vendor's official channels for a formal patch release and apply it once available. No workarounds are currently known.

Description

libgphoto2 is a camera access and control library. In versions up to and including 2.5.33, an out of bound read in ptp_unpack_EOS_FocusInfoEx could be used to crash libgphoto2 when processing input from untrusted USB devices. Commit c385b34af260595dfbb5f9329526be5158985987 contains a patch. No known workarounds are available.

References

Community reviews

Loading reviews…