Skip to content
IoT

CVE-2026-71264

8.2
High
EPSS 0.19%Aug 5, 2026

WLED exposes config and a global PIN state allows persistent unauthenticated config writes

common questions

Is CVE-2026-71264 being exploited?

Not confirmed. CVE-2026-71264 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-71264?

CVE-2026-71264 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-71264?

Not known from our data. No patch reference has been recorded for CVE-2026-71264, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-71264 affect?

CVE-2026-71264 affects WLED (wled_server), ESP8266/ESP32 devices running WLED, Devices exposing /json API on local network. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71264?

Isolate/segment WLED devices, block/limit /json API, reboot devices to clear PIN, apply vendor patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WLED (wled_server)ESP8266/ESP32 devices running WLEDDevices exposing /json API on local network
impact

Local unauthenticated attackers can read device config; if any client submits the 4‑digit PIN, all clients gain persistent write access to push OTA firmware, change Wi‑Fi, or factory reset.

action required

Immediate action required

affected versions
Aircoookie WLED
  • affected<= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free