CVE-2026-28522
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 a null pointer dereference vulnerability in the WiFiUDP component. An attacker on the same local area network can send a large volume of malicious UDP packets that trigger a null pointer dereference, resulting in 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 · moderate confidenceThe arduino-TuyaOpen library before version 1.2.1 contains a null pointer dereference vulnerability in its WiFiUDP component. An attacker on the same local network can send a large volume of malicious UDP packets that trigger the null pointer dereference, causing the device to crash and resulting in 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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 the installed arduino-TuyaOpen library versionLocate the arduino-TuyaOpen library files in your Arduino libraries folder and check the library.properties file for the version number, or use the Arduino Library Manager to view the installed versionAffected if The installed version is any version prior to 1.2.1 (e.g., 1.2.0, 1.1.0, etc.)
-
Verify the WiFiUDP component is in useSearch your project source files for includes of the WiFiUDP.h header or references to the WiFiUDP class in your sketchAffected if Your code imports or uses the WiFiUDP component from the arduino-TuyaOpen library
-
Confirm network exposure to untrusted devicesReview your network configuration to determine whether devices on the same local network can send UDP packets to the vulnerable device without firewall or access control restrictionsAffected if The device is accessible to untrusted or attacker-controlled devices on the local network via UDP traffic
Your environment is affected if you have arduino-TuyaOpen library versions prior to 1.2.1 that use the WiFiUDP component and are accessible to untrusted devices on the same network.
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 patched code. Additionally, implement network segmentation and firewall rules to restrict untrusted devices from sending UDP traffic to vulnerable devices on the local network.
1.2.1 or later
- 1. Identify all instances of Arduino TuyaOpen in your deployment that are running versions prior to 1.2.1
- 2. Consult the official Arduino TuyaOpen repository (github.com) or Tuya documentation (src.tuya.com) to obtain version 1.2.1 or later
- 3. Backup existing firmware/images before upgrading
- 4. Upgrade the WiFiUDP component or entire TuyaOpen library to version 1.2.1 or latest stable release
- 5. Verify the upgrade was successful by checking the installed version
- 6. Test the UDP functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28522 — 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-28522 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