# Samsung One vulnerabilities Source: https://junglewise.ai/threats/technologies/samsung-one Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats Updated: 10 November 2026, 03:07 UTC. Rebuilt every hour. Data: https://junglewise.ai/threats/technologies/samsung-one.json License: CC BY 4.0 with a link back Junglewise Threat Intelligence has tracked 9 vulnerabilities in Samsung One: 0 in the last 7 days and 0 in the last 90 days, 0 of them critical and 0 exploited in the wild. The most recent, CVE-2026-6840, was published on 22 April 2026. ## Counts - Last 7 days: 0 - Last 30 days: 0 - Last 90 days: 0 - All time: 9 (0 critical, 0 exploited in the wild) ## Latest Samsung One vulnerabilities - [CVE-2026-6840: Missing bounds validation for operator could allow out of range operator-code lookup during model loading Affected…](https://junglewise.ai/threats/cve-2026-6840-missing-bounds-validation-for-operator-could-allow-out-of-range) (medium, CVSS 5.5, published 22 Apr 2026) - [CVE-2026-6839: Improper validation of STRING tensor offsets could allows malformed string metadata to trigger out of bounds access…](https://junglewise.ai/threats/cve-2026-6839-improper-validation-of-string-tensor-offsets-could-allows) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41667: Integer overflow in constant tensor data size calculation in Samsung Open Source ONE could cause incorrect buffer…](https://junglewise.ai/threats/cve-2026-41667-integer-overflow-in-constant-tensor-data-size-calculation-in) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41666: Integer overflow in tensor copy size calculation in Samsung Open Source ONE could lead to out of bounds access during…](https://junglewise.ai/threats/cve-2026-41666-integer-overflow-in-tensor-copy-size-calculation-in-samsung-open) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41665: Integer overflow in scratch buffer initialization size calculation in Samsung Open Source ONE cause incorrect memory…](https://junglewise.ai/threats/cve-2026-41665-integer-overflow-in-scratch-buffer-initialization-size) (medium, CVSS 6.1, published 22 Apr 2026) - [CVE-2026-41664: Integer overflow in memory copy size calculation in Samsung Open Source ONE could lead to invalid memory operations…](https://junglewise.ai/threats/cve-2026-41664-integer-overflow-in-memory-copy-size-calculation-in-samsung-open) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-40450: Integer overflow in output tensor copy size calculation in Samsung Open Source ONE could cause incorrect copy length…](https://junglewise.ai/threats/cve-2026-40450-integer-overflow-in-output-tensor-copy-size-calculation-in) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-40449: Integer overflow in buffer size calculation could result in out of bounds memory access when handling large tensors in…](https://junglewise.ai/threats/cve-2026-40449-integer-overflow-in-buffer-size-calculation-could-result-in-out) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-40448: Potential Integer overflow in tensor allocation size calculation could lead to insufficient memory allocation for…](https://junglewise.ai/threats/cve-2026-40448-potential-integer-overflow-in-tensor-allocation-size-calculation) (medium, CVSS 5.3, published 22 Apr 2026) ## Most severe Samsung One vulnerabilities - [CVE-2026-41667: Integer overflow in constant tensor data size calculation in Samsung Open Source ONE could cause incorrect buffer…](https://junglewise.ai/threats/cve-2026-41667-integer-overflow-in-constant-tensor-data-size-calculation-in) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41666: Integer overflow in tensor copy size calculation in Samsung Open Source ONE could lead to out of bounds access during…](https://junglewise.ai/threats/cve-2026-41666-integer-overflow-in-tensor-copy-size-calculation-in-samsung-open) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-40450: Integer overflow in output tensor copy size calculation in Samsung Open Source ONE could cause incorrect copy length…](https://junglewise.ai/threats/cve-2026-40450-integer-overflow-in-output-tensor-copy-size-calculation-in) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-40449: Integer overflow in buffer size calculation could result in out of bounds memory access when handling large tensors in…](https://junglewise.ai/threats/cve-2026-40449-integer-overflow-in-buffer-size-calculation-could-result-in-out) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-6839: Improper validation of STRING tensor offsets could allows malformed string metadata to trigger out of bounds access…](https://junglewise.ai/threats/cve-2026-6839-improper-validation-of-string-tensor-offsets-could-allows) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41664: Integer overflow in memory copy size calculation in Samsung Open Source ONE could lead to invalid memory operations…](https://junglewise.ai/threats/cve-2026-41664-integer-overflow-in-memory-copy-size-calculation-in-samsung-open) (medium, CVSS 6.6, published 22 Apr 2026) - [CVE-2026-41665: Integer overflow in scratch buffer initialization size calculation in Samsung Open Source ONE cause incorrect memory…](https://junglewise.ai/threats/cve-2026-41665-integer-overflow-in-scratch-buffer-initialization-size) (medium, CVSS 6.1, published 22 Apr 2026) - [CVE-2026-6840: Missing bounds validation for operator could allow out of range operator-code lookup during model loading Affected…](https://junglewise.ai/threats/cve-2026-6840-missing-bounds-validation-for-operator-could-allow-out-of-range) (medium, CVSS 5.5, published 22 Apr 2026) - [CVE-2026-40448: Potential Integer overflow in tensor allocation size calculation could lead to insufficient memory allocation for…](https://junglewise.ai/threats/cve-2026-40448-potential-integer-overflow-in-tensor-allocation-size-calculation) (medium, CVSS 5.3, published 22 Apr 2026) ## Vulnerabilities per week Nothing was published in the last eight weeks. | Week of | Vulns | Critical | Exploited | | --- | --- | --- | --- | | 17 Aug 2026 | 0 | 0 | 0 | | 24 Aug 2026 | 0 | 0 | 0 | | 31 Aug 2026 | 0 | 0 | 0 | | 7 Sep 2026 | 0 | 0 | 0 | | 14 Sep 2026 | 0 | 0 | 0 | | 21 Sep 2026 | 0 | 0 | 0 | | 28 Sep 2026 | 0 | 0 | 0 | | 5 Oct 2026 | 0 | 0 | 0 | | 12 Oct 2026 | 0 | 0 | 0 | | 19 Oct 2026 | 0 | 0 | 0 | | 26 Oct 2026 | 0 | 0 | 0 | | 2 Nov 2026 | 0 | 0 | 0 | | 9 Nov 2026 | 0 | 0 | 0 | ## Other Samsung technologies - [Samsung Exynos 1380](https://junglewise.ai/threats/technologies/exynos-1380): 37 vulnerabilities - [Samsung Exynos 1480](https://junglewise.ai/threats/technologies/exynos-1480): 37 vulnerabilities - [Samsung Exynos 1580](https://junglewise.ai/threats/technologies/exynos-1580): 37 vulnerabilities - [Samsung Exynos 2400](https://junglewise.ai/threats/technologies/exynos-2400): 33 vulnerabilities - [Samsung Exynos 1330](https://junglewise.ai/threats/technologies/exynos-1330): 30 vulnerabilities - [Samsung Escargot](https://junglewise.ai/threats/technologies/escargot): 28 vulnerabilities - [Samsung Exynos 2500](https://junglewise.ai/threats/technologies/exynos-2500): 27 vulnerabilities - [Samsung Exynos 1280](https://junglewise.ai/threats/technologies/exynos-1280): 25 vulnerabilities - [Samsung Exynos 2200](https://junglewise.ai/threats/technologies/exynos-2200): 20 vulnerabilities - [Samsung Exynos W920](https://junglewise.ai/threats/technologies/exynos-w920): 19 vulnerabilities - [Samsung Exynos 850](https://junglewise.ai/threats/technologies/exynos-850): 18 vulnerabilities - [Samsung Exynos W930](https://junglewise.ai/threats/technologies/exynos-w930): 18 vulnerabilities ## Sources NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories. Rebuilt every hour. Cite as: Junglewise Threat Intelligence, "Samsung One vulnerabilities", https://junglewise.ai/threats/technologies/samsung-one, 10 November 2026.