One (Samsung) - vulnerabilities (CVEs)
9 CVEs, 0 in the last 30 days, 38 known versions, newest CVE from 2026-04-22. Vendor: Samsung.
CVEs of One
- CVE-2026-6840 - CVSS 5.5 (medium), 2026-04-22: Missing bounds validation for operator could allow out of range operator-code lookup during model loading Affected version is prior to commit 1.30.0.
- CVE-2026-6839 - CVSS 6.6 (medium), 2026-04-22: Improper validation of STRING tensor offsets could allows malformed string metadata to trigger out of bounds access during constant tensor import in Samsung…
- CVE-2026-40449 - CVSS 6.6 (medium), 2026-04-22: Integer overflow in buffer size calculation could result in out of bounds memory access when handling large tensors in Samsung Open Source ONE. Affected…
- CVE-2026-41665 - CVSS 6.1 (medium), 2026-04-22: Integer overflow in scratch buffer initialization size calculation in Samsung Open Source ONE cause incorrect memory initialization for large intermediate…
- CVE-2026-41664 - CVSS 6.6 (medium), 2026-04-22: Integer overflow in memory copy size calculation in Samsung Open Source ONE could lead to invalid memory operations with large tensor shapes. Affected version…
- CVE-2026-41667 - CVSS 6.6 (medium), 2026-04-22: Integer overflow in constant tensor data size calculation in Samsung Open Source ONE could cause incorrect buffer sizing for large constant nodes. Affected…
- CVE-2026-40450 - CVSS 6.6 (medium), 2026-04-22: Integer overflow in output tensor copy size calculation in Samsung Open Source ONE could cause incorrect copy length and memory corruption for oversized…
- CVE-2026-41666 - CVSS 6.6 (medium), 2026-04-22: Integer overflow in tensor copy size calculation in Samsung Open Source ONE could lead to out of bounds access during loop state propagation. Affected version…
- CVE-2026-40448 - CVSS 5.3 (medium), 2026-04-22: Potential Integer overflow in tensor allocation size calculation could lead to insufficient memory allocation for large tensors in Samsung Open Source ONE.…