Cyber Resilience

CVE-2026-28519

Memory Safety in Arduino-Tuyaopen ≤ 1.2.1

Public PoCMemory Safety
Published
16 March 2026
Modified
17 March 2026
Patch / advisory
View advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/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:X
EPSS Score 0.0040 33th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2026-28519 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Tuya Arduino-Tuyaopen. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 33th 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 SI-10 (Information Input Validation) — 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-28519 is a heap-based buffer overflow vulnerability (CWE-122) affecting the arduino-TuyaOpen library prior to version 1.2.1, specifically in its DnsServer component. Published on 2026-03-16, this flaw has a CVSS v3.1 base score of 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). It impacts embedded devices utilizing this open-source Arduino library for integration with Tuya's IoT platform.

An attacker on the same local area network (LAN) who controls the LAN DNS server can exploit the vulnerability by sending crafted malicious DNS responses. This triggers a heap buffer overflow in the DnsServer component, potentially enabling arbitrary code execution on the targeted embedded device with high confidentiality, integrity, and availability impacts.

Advisories recommend updating to arduino-TuyaOpen version 1.2.1 or later to mitigate the issue, as detailed in the project's GitHub repository (https://github.com/tuya/arduino-TuyaOpen), Tuya's announcement (https://src.tuya.com/announcement/32), and VulnCheck's advisory (https://www.vulncheck.com/advisories/arduino-tuyaopen-dnsserver-heap-based-buffer-overflow-remote-code-execution).

EU & UK References

Vulnerability Data

arduino-TuyaOpen before version 1.2.1 contains a heap-based buffer overflow vulnerability in the DnsServer component. An attacker on the same local area network who controls the LAN DNS server can send malicious DNS responses to overflow the heap buffer, potentially allowing…

more

execution of arbitrary code on affected embedded devices.

CWE(s)
CWE-122

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28520Same product: Tuya Arduino-Tuyaopen
CVE-2026-28521Same product: Tuya Arduino-Tuyaopen
CVE-2026-28522Same product: Tuya Arduino-Tuyaopen
CVE-2024-29982Shared CWE-122
CVE-2024-49011Shared CWE-122
CVE-2025-54282Shared CWE-122
CVE-2026-5868Shared CWE-122
CVE-2026-23534Shared CWE-122
CVE-2026-50477Shared CWE-122
CVE-2026-62736Shared CWE-122

Affected Assets

tuya
arduino-tuyaopen
≤ 1.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

SI-10 Information Input Validation good match

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

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.

PR.PS-06 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Timely patching removes known heap-overflow instances after they exist.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect heap overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

A.8.32 Change management none match
none

Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.

References