CVE-2026-28520
Arduino-Tuyaopen ≤ 1.2.1
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-28520 is a high-severity Off-by-one Error (CWE-193) vulnerability in Tuya Arduino-Tuyaopen. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-28520 is a single-byte buffer overflow vulnerability (CWE-193) in the WiFiMulti component of the arduino-TuyaOpen library prior to version 1.2.1. This affects embedded smart hardware devices that utilize the library for WiFi connectivity integration with Tuya's IoT platform. The issue, published on 2026-03-16, carries a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high confidentiality, integrity, and availability impacts.
An attacker can exploit the vulnerability by controlling an access point (AP) hotspot to which the victim's smart hardware connects. No privileges are required (PR:N), and exploitation occurs with low complexity (AC:L) upon connection, allowing the attacker to trigger the buffer overflow and achieve remote code execution on the affected embedded device.
Mitigation involves upgrading to arduino-TuyaOpen version 1.2.1 or later, as indicated by the vulnerability's versioning details. Additional guidance is available in the Tuya announcement at https://src.tuya.com/announcement/32, the project repository at https://github.com/tuya/arduino-TuyaOpen, and the VulnCheck advisory at https://www.vulncheck.com/advisories/arduino-tuyaopen-wifimulti-single-byte-buffer-overflow-remote-code-execution.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12227
Vulnerability Data
arduino-TuyaOpen before version 1.2.1 contains a single-byte buffer overflow vulnerability in the WiFiMulti component. When the victim's smart hardware connects to an attacker-controlled AP hotspot, the attacker can exploit the overflow to execute arbitrary code on the affected embedded device.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.
Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect off-by-one errors before release.
Secure development life cycle includes requirements and reviews that can catch off-by-one errors.
Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.
Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.
Secure coding directly addresses off-by-one errors through coding standards and peer review.