CVE-2026-28521
Out-of-Bounds Read in TuyaIoT Causes Data Leak, DoS
Publication date: 2026-03-16
Last updated on: 2026-03-17
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tuya | arduino-tuyaopen | to 1.2.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-28521 is a high-severity vulnerability in arduino-TuyaOpen versions before 1.2.1. It is an out-of-bounds memory read issue in the TuyaIoT component. An attacker who hijacks or controls the Tuya cloud service can send malicious DP event data to affected devices. This causes the device to access memory outside its intended boundaries, which can lead to unintended behavior.
- The vulnerability is classified as CWE-125 (out-of-bounds memory read).
- It does not require user interaction, privileges, or authentication.
- The attack vector is local with high complexity.
- The issue was fixed in version 1.2.1 of arduino-TuyaOpen.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker who controls the Tuya cloud service to cause out-of-bounds memory access on your device. This can lead to two main consequences:
- Information disclosure: Sensitive data may be exposed due to unauthorized memory reads.
- Denial-of-service: The device may crash or become unresponsive, disrupting its normal operation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update arduino-TuyaOpen to version 1.2.1 or later, where the issue has been fixed.
Since the vulnerability arises from malicious DP event data sent via the Tuya cloud service, controlling or restricting access to the Tuya cloud service and monitoring for suspicious activity may also help reduce risk.