CVE-2026-75491 in TR3000
Summary
by MITRE • 11/13/2026
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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in the Cudy TR3000 router firmware prior to version 2.5.42 represents a critical authentication bypass flaw within its Mosquitto MQTT broker implementation, specifically affecting the JWT-based authentication plugin named auth_plugin_jwt.so. This security defect stems from an improper validation of JSON Web Tokens (JWTs) where the system fails to enforce cryptographic signature verification for tokens utilizing the none algorithm. In standard JWT implementations, the alg header specifies the signing algorithm used to secure the token's integrity and authenticity. By accepting unsigned tokens with alg set to none, the authentication mechanism effectively disables proof-of-possession requirements, allowing any entity presenting a valid client certificate trusted by the Cudy ecosystem to forge or manipulate credentials without possessing the private key associated with the intended user identity. This flaw fundamentally undermines the trust model established by Public Key Infrastructure (PKI) implementations in IoT devices, as it decouples authentication from actual cryptographic proof of ownership.
From an operational perspective, this vulnerability allows remote attackers who possess a Cudy-trusted client certificate to bypass administrative controls entirely. The attacker can authenticate as the privileged user admincudydevice over port 8883, which is typically reserved for secure MQTT communications using Transport Layer Security (TLS). Once authenticated with these elevated privileges, the adversary gains the ability to publish batchcmd requests directly into the broker's message queue. These commands are subsequently executed by the underlying system processes with root-level permissions, granting full control over the device. This level of access enables a wide range of malicious activities including network reconnaissance, configuration tampering, installation of persistent backdoors, and potentially using the compromised router as a pivot point for lateral movement within the local network or further attacks against connected IoT devices.
The technical classification of this flaw aligns with CWE-287 Improper Authentication, specifically highlighting the failure to verify cryptographic signatures during the authentication process. It also relates closely to CWE-345 Insufficient Verification of Data Authenticity, as the system accepts data that has not been cryptographically signed despite security policies expecting such verification. In terms of offensive cyber operations and threat modeling, this vulnerability maps directly to MITRE ATT&CK technique T1078 Valid Accounts, where adversaries leverage legitimate credentials or forged tokens to gain unauthorized access. Furthermore, the ability to execute arbitrary commands as root corresponds to privilege escalation vectors often seen in embedded systems with weak separation between service-level permissions and system-level administrative rights. The exploitation of this flaw does not require complex buffer overflow techniques or memory corruption exploits; instead, it relies on logical flaws in protocol handling and configuration enforcement, making it highly reliable and easy to automate for widespread attacks against vulnerable firmware versions.
Mitigation strategies must focus primarily on immediate software updates. Administrators should upgrade the Cudy TR3000 router firmware to version 2.5.42 or later, where this authentication bypass has been remediated by enforcing strict validation of JWT signatures and rejecting tokens with alg none unless explicitly permitted for specific non-security contexts that do not involve administrative access. For environments where immediate patching is not feasible, network segmentation should be employed to restrict access to port 8883 only from trusted subnets or management VLANs. Additionally, organizations should audit their PKI infrastructure to ensure that client certificates are issued with appropriate constraints and that the private keys associated with these certificates are stored securely on hardware security modules or secure enclaves rather than in easily accessible file systems. Regular vulnerability scanning of IoT assets using specialized tools capable of detecting MQTT misconfigurations can help identify other instances of this weakness across an enterprise network before exploitation occurs.