Shenzhen Cudy TR3000 auth bypass via unsigned JWTs in MQTT plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.42
- Who is exposed
- Not reported
Summary
Shenzhen Cudy Technology Co., Ltd.'s Cudy TR3000 contains an authentication bypass in its MQTT plugin, which accepts unsigned JWTs using the "none" algorithm. An attacker who holds any Cudy-trusted client certificate can reach it remotely over the network without logging in, authenticate as admincudydevice on port 8883, and publish batchcmd requests to run commands as root.
Written by a model
Original description
Cudy TR3000 before 2.5.42 contains an authentication bypass vulnerability in the Mosquitto plugin auth_plugin_jwt.so that accepts unsigned JWTs using alg none. Attackers holding any Cudy-trusted client certificate can authenticate as admincudydevice on port 8883 and publish batchcmd requests to execute commands as root.
Who should check
Teams running Cudy TR3000 1.0 routers with firmware before 2.5.42 that use the Mosquitto JWT auth plugin for MQTT on port 8883
“Cudy TR3000 before 2.5.42 contains an authentication bypass vulnerability in the Mosquitto plugin auth_plugin_jwt.so”
What to do
Upgrade to a fixed version: 2.5.42.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-75491 (Cudy TR3000 before 2.5.42 MQTT JWT Authentication Bypass via alg none Tokens), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-75491 (entry last updated 2026-11-18):
Affected:
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0: fixed in 2.5.42
Fixed versions: 2.5.42.
Conditions (all must be true for the bug to be hit):
- Cudy TR3000 firmware before 2.5.42 with the Mosquitto plugin auth_plugin_jwt.so in use (source: https://www.cudy.com/pages/security-advisory/cudy-sa-26-11-vv-7-cft)
- Attacker holds a Cudy-trusted client certificate (source: https://www.cudy.com/pages/security-advisory/cudy-sa-26-11-vv-7-cft)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-75491 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75491 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.cudy.com/pages/security-advisory/cudy-sa-26-11-vv-7-cft
- https://d1jvyy13vm72kv.cloudfront.net/device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip
- https://www.cudy.com/en-us/pages/download-center/tr3000-1-0
- https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-mqtt-jwt-authentication-bypass-via-alg-none-tokens
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-75491
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75491"}.Affected versions
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0fixed in 2.5.42
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.2, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now5 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.19%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | cudy.com · pages/security-advisory/cudy-sa-26-11-vv-7-cft |
| Link | cudy.com · en-us/pages/download-center/tr3000-1-0 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-75491 |
| Record | NVD · CVE-2026-75491 |
| Other links 2 | |
| Patch | d1jvyy13vm72kv.cloudfront.net · device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip |
| Link | vulncheck.com · advisories/cudy-tr3000-before-2.5.42-mqtt-jwt-authentication-bypass-via-alg-none-tokens |
Questions about CVE-2026-75491
Is CVE-2026-75491 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Mosquitto JWT authentication plugin on the Cudy TR3000 accepts JWT tokens that use the alg none setting, so an attacker can authenticate as the admincudydevice MQTT user without a valid signature. The advisory says that user can then publish batchcmd requests that run commands as root on the device.
Source: cudy.com
Which versions are affected by CVE-2026-75491?
TR3000 1.0: before 2.5.42.
Source: cve.now feed data
Am I affected, and how do I check?
Firmware before 2.5.42 on the TR3000 1.0 is affected when the Mosquitto plugin auth_plugin_jwt.so is in use on port 8883, and the attacker must hold a Cudy-trusted client certificate. To check, look at the firmware version in the router's system information and whether the JWT auth plugin is enabled in the Mosquitto configuration.
Source: cudy.com
How do I fix CVE-2026-75491?
Update the firmware to 2.5.42 or later, which is the fixed version listed for this vulnerability.
Source: cudy.com
Related
- CVE-2026-75495Cudy TR3000 before 2.5.42 OS Command Injection via TR-098 User Password Parameter
- CVE-2026-126953Cudy TR3000 before 2.5.42 OS Command Injection via TR-098 User Username
- CVE-2026-75492Cudy TR3000 before 2.5.42 Stack Buffer Overflow via stun_client UDP Parser
- CVE-2026-129099Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Configuration Import
- CVE-2026-129100Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Key Upload Injection
- CVE-2026-129101Cudy TR3000 before 2.5.42 Authenticated RCE via vpn.set_conf Mass Assignment
No corrections so far. Something wrong on this page? Report an error.