dbcve.org
Arduino TuyaopenApplication · Tuya

CVE-2026-28520

HIGH · 8.4 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

A single-byte buffer overflow vulnerability in the WiFiMulti component of arduino-TuyaOpen versions prior to 1.2.1 allows remote code execution. When a victim's smart hardware device connects to an attacker-controlled malicious AP hotspot, the attacker can exploit the overflow to achieve arbitrary code execution on the embedded device.

MitigationUpgrade arduino-TuyaOpen library to version 1.2.1 or later. For deployed devices, firmware updates may be required to incorporate the patched library.

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
Arduino TuyaopenApplication
Affected:< 1.2.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the arduino-TuyaOpen library in your project
    Search your Arduino project directory or libraries folder for folders named 'TuyaOpen', 'Tuya', or 'arduino-TuyaOpen'. Check your platformio.ini or Arduino IDE library.json for dependencies referencing this library.
    Affected if The arduino-TuyaOpen library is present in your project dependencies or library folder.
  2. Identify the installed version of arduino-TuyaOpen
    Open the library.properties, version.txt, or package.json file within the TuyaOpen library folder and locate the version field. Compare this to the affected range of versions before v1.2.1.
    Affected if The library version is lower than 1.2.1 (for example, 1.2.0, 1.1.0, or any version without the patch).
  3. Verify usage of the WiFiMulti component
    Search your project source code (.ino, .cpp, .h files) for includes of WiFiMulti.h or WiFiMulti headers, and look for WiFiMulti object instantiation or function calls such as addAP(), run(), or loop().
    Affected if Your code instantiates or uses a WiFiMulti object to manage WiFi access point connections.
  4. Confirm the device has WiFi connectivity enabled
    Review your hardware configuration or firmware build settings to verify the device is configured to connect to WiFi networks. Check for WiFi.mode() or WiFi.begin() calls in your code.
    Affected if The firmware includes WiFi functionality and the device is intended to connect to wireless networks.

Your environment is affected if arduino-TuyaOpen library version is below 1.2.1 and your code uses the WiFiMulti component to connect devices to WiFi access points.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2.1 or later
Fixed in 1.2.1
Interim mitigation

Upgrade arduino-TuyaOpen library to version 1.2.1 or later. For deployed devices, firmware updates may be required to incorporate the patched library.

Recommended fix High confidence

Arduino TuyaOpen version 1.2.1

  1. 1. Identify the current version of arduino-TuyaOpen library in use by checking the library.properties file or IDE library manager
  2. 2. Open Arduino IDE or platform-specific library management tool
  3. 3. Navigate to Library Manager and search for 'TuyaOpen'
  4. 4. Upgrade to version 1.2.1 or latest available version
  5. 5. Rebuild and recompile the firmware project
  6. 6. Flash the updated firmware to the affected smart hardware device
  7. 7. Verify the device functions correctly with the updated library

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arduino Tuyaopen Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28520 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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