Skip to content
IoT

CVE-2026-71960

9.3
Critical
EPSS 0.54%Patch availableAug 20, 2026

Hard-coded JWT HMAC secret in Cudy WR3000 allows forged JWTs to access MQTT mesh.

common questions

Is CVE-2026-71960 being exploited?

Not confirmed. CVE-2026-71960 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.54% probability of exploitation in the next 30 days.

How severe is CVE-2026-71960?

CVE-2026-71960 is rated Critical with a CVSS score of 9.3. 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-71960?

Yes. A fix has been recorded for CVE-2026-71960. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-71960 affect?

CVE-2026-71960 affects Cudy WR3000 (firmware < 2.5.24), Mosquitto MQTT broker auth plugin on Cudy devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71960?

Upgrade firmware to 2.5.24+, disable external MQTT, isolate affected devices, rotate credentials.

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

executive summary
technical analysis
affected
Cudy WR3000 (firmware < 2.5.24)Mosquitto MQTT broker auth plugin on Cudy devices
impact

Extractable hard-coded JWT HMAC secret lets unauthenticated attackers forge tokens, authenticate to Mosquitto MQTT, and access/control the device's mesh interface.

action required

Immediate action required

affected versions
Shenzhen Cudy Technology Co., Ltd. P5 V1.1
  • affected>= 2.4.25 and <= 2.4.27
Shenzhen Cudy Technology Co., Ltd. WR3000 2.0
  • affected< 2.5.24

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