Skip to content
Fencer Intel
high 7.3

CVE-2026-69005 json

Integer overflow in NPU driver parameter processing due to insufficient bounds checking.

published 7d ago modified yesterday also EUVD-2026-117290

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

Integer overflow in NPU driver parameter processing due to insufficient bounds checking.

Patch / fix

  • Samsung Semiconductor Exynos 1480 November 2026
  • Samsung Semiconductor Exynos 2400 November 2026
  • Samsung Semiconductor Exynos 1580 November 2026
  • Samsung Semiconductor Exynos 2500 November 2026
  • Samsung Semiconductor Exynos 2600 November 2026
  • Samsung Semiconductor Exynos 1680 November 2026

Is CVE-2026-69005 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected products

  • Samsung Semiconductor Exynos 1480
  • Samsung Semiconductor Exynos 2400
  • Samsung Semiconductor Exynos 1580
  • Samsung Semiconductor Exynos 2500
  • Samsung Semiconductor Exynos 2600
  • Samsung Semiconductor Exynos 1680

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.