CVE-2026-28521
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedarduino-TuyaOpen before version 1.2.1 contains an out-of-bounds memory read vulnerability in the TuyaIoT component. An attacker who hijacks or controls the Tuya cloud service can issue malicious DP event data to victim devices, causing out-of-bounds memory access that may result in information disclosure or a denial-of-service condition.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an out-of-bounds memory read vulnerability in the TuyaIoT component of the arduino-TuyaOpen library (versions before 1.2.1). An attacker who compromises the Tuya cloud service can send malicious DP (Data Point) event data to connected devices, causing the device to read memory outside allocated buffers. This can expose sensitive information from device memory or cause a denial-of-service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify arduino-TuyaOpen library versionOpen Arduino IDE, go to Sketch > Include Library > Manage Libraries, search for 'TuyaOpen' and check the installed version. Alternatively, check the library.properties file in the library folder for the version field.Affected if The version listed is below 1.2.1 (e.g., 1.2.0, 1.1.0, etc.)
-
Locate TuyaIoT component in projectSearch project source files for '#include <TuyaIoT.h>' or similar TuyaIoT header includes. Check for TuyaIoT object instantiation in the sketch.Affected if TuyaIoT headers are included or TuyaIoT objects are instantiated in the code, indicating the vulnerable component is in use
-
Verify device connects to Tuya cloudExamine the sketch for TuyaCloudDiy or TuyaCloudWIFI initialization calls, and look for network configuration pointing to Tuya cloud endpoints.Affected if The device code initializes a connection to Tuya cloud service, which is the attack vector for delivering malicious DP events
-
Check for DP event handling codeSearch for DP (Data Point) related function handlers such as 'dpUpdate', 'onDpUpdate', or 'mydevice.sendDPCmd' in the source code.Affected if The sketch processes DP events from the cloud, which is the input vector for the out-of-bounds read vulnerability
The device is affected if the arduino-TuyaOpen library version is below 1.2.1 AND the TuyaIoT component is actively used to receive DP event data from Tuya cloud services.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.1
Upgrade arduino-TuyaOpen to version 1.2.1 or later to obtain the patch. Consider network monitoring to detect anomalous cloud-to-device communications as an additional safeguard.
arduino-TuyaOpen version 1.2.1
- Open Arduino IDE and navigate to Sketch > Include Library > Manage Libraries
- Search for "TuyaOpen" in the Library Manager
- Locate the arduino-TuyaOpen library in the search results
- Check the current installed version - if it is below 1.2.1, an update is needed
- Click the "Update" button next to the library to upgrade to the latest version (1.2.1 or later)
- Wait for the download and installation to complete
- Verify the upgrade was successful by checking the library version in the Library Manager
- Rebuild and redeploy any affected IoT firmware to devices using this library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28521 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data