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.
CVE-2026-120451
MEDIUMPre-NVD 6.86.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-11-02. A secondary CVSS source baseline 6.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-115211 (ENISA EUVD) · GHSA-7rfg-j54g-6xm2 (GitHub Security Advisories)Source: ENISA EUVD
6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.8
- EG Score
- 6.8MEDIUMhigh confidence
- EG Risk
- 47EG Risk 47/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity68% × 45%Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 13th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 2, 2026
Last Modified
November 6, 2026
Advisory Details (6)
Auto-updated Nov 2, 2026Patch available. Sources: github_commit.
Web page
libgphoto2 through 2.5.34 Buffer Overflow via jl2005c Camera Driver | Advisories | VulnCheck
https://www.vulncheck.com/advisories/libgphoto2-through-2.5.34-buffer-overflow-via-jl2005c-camera-driverWeb page
libgphoto2 Jeilin JL2005 driver: a device-supplied entry count drives stack and heap buffer overflows during camera initialization - HackMD
https://hackmd.io/@haindpwn/libgphoto2-jl2005c-init-alloc-table-buffer-overflowWeb page
libgphoto2/camlibs/jl2005c/jl2005c.c at v2.5.34 · gphoto/libgphoto2 · GitHub
https://github.com/gphoto/libgphoto2/blob/v2.5.34/camlibs/jl2005c/jl2005c.c#L138-L154GitHub commit
commit 6a3393dd9965 (gphoto/libgphoto2)
Fix landed in gphoto/libgphoto2 commit 6a3393dd9965 — awaiting tagged release
https://github.com/gphoto/libgphoto2/commit/6a3393dd996502457ab965432cf0b2035278825eGitHub commit
commit af3b8e9c542c (gphoto/libgphoto2)
Fix landed in gphoto/libgphoto2 commit af3b8e9c542c — awaiting tagged release
https://github.com/gphoto/libgphoto2/commit/af3b8e9c542cda863fb5f2f3cfeb261bd78e4442Web page
libgphoto2 Jeilin JL2005 driver: a device-supplied entry count drives stack and heap buffer overflows during camera initialization · Issue #1326 · gphoto/libgphoto2 · GitHub
https://github.com/gphoto/libgphoto2/issues/1326Vendor Advisories for CVE-2026-120451(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libgphoto2-port12 (2.5.27-1ubuntu0.2) @ jammy | 2026-11-11 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libgphoto2 | 2.5.30-1 ... 2.5.34-2 (11 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libgphoto2 | 2.5.31-4, 2.5.32-1, 2.5.33-1, 2.5.34-1, 2.5.34-2 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libgphoto2 | 2.5.31-4, 2.5.32-1, 2.5.33-1, 2.5.34-1, 2.5.34-2 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 12× in last 7d / 20× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-11 07:03 UTCEchelonGraph re-scored
- 2026-11-11 07:03 UTCVendor advisory
- 2026-11-11 07:03 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-06 21:26 UTCEchelonGraph re-scored
- 2026-11-06 21:26 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-06 20:28 UTCEchelonGraph re-scored
- 2026-11-06 20:28 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-06 19:37 UTCEchelonGraph re-scored
- 2026-11-06 19:37 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-04 01:50 UTCEchelonGraph re-scored
- 2026-11-04 01:50 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-02 19:47 UTCEchelonGraph re-scored
- 2026-11-02 19:47 UTCGHSA enrichmentGHSA-7rfg-j54g-6xm2 · GitHub severity HIGH · GitHub CVSS 6.8
- 2026-11-02 16:03 UTCENISA EUVD ID recordedEUVD-2026-115211 · Source: ENISA EUVD
Show 3 moreShow fewer
- 2026-11-02 15:28 UTCEchelonGraph re-scored
- 2026-11-02 14:32 UTCEchelonGraph re-scoredFirst assessed: 6.8 MEDIUM
- 2026-11-02 14:32 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
9 shownDebian:12:libgphoto2
Frequently asked(5)
What is CVE-2026-120451?
CVE-2026-120451 is a medium-severity vulnerability; its CVE record was published on November 2, 2026. 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…
When was CVE-2026-120451 made public?
CVE-2026-120451 was made public on October 22, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 2, 2026. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-120451 actively exploited?
CVE-2026-120451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120451?
CVE-2026-120451 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120451?
A fix for CVE-2026-120451 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-120451 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-120451
Is Your Infrastructure Affected by CVE-2026-120451?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.