Summary
CVE-2026-82452 is a critical missing-authentication vulnerability (CWE-306) affecting rust-iot-platform, an open-source Rust-based IoT backend maintained by iot-ecology. Most REST API route handlers — including those in the user management controller — are defined without any authentication guard, allowing unauthenticated network attackers to create, list, retrieve, update, and delete user accounts. The issue affects all code through commit 5df942ab6bc46a3bf83dbee8c7970554f92c972d and carries a severity of 9.3 (CVSS v4.0) / 9.8 (CVSS v3.1), both rated Critical.
Technical details
- Root cause: Route handler functions in
api/src/controller/user_router.rs(e.g.,create_user,update_user,delete_user,page_user,list_user,by_id_user) are implemented using the Rocket web framework but do not include any Rocket request guard or middleware that verifies caller identity before the handler logic executes. - Trigger conditions: No special preconditions are required — an attacker simply needs network access to the exposed API; no valid session, token, or credential is checked.
- Attack vector: Network (remote, unauthenticated); no user interaction and low attack complexity (AV:N/AC:L/PR:N/UI:N).
- Impact: Full compromise of user account data and management functions — attackers can enumerate all user accounts, read account details, create new accounts, modify existing accounts, and delete accounts, with high impact to confidentiality, integrity, and availability of the affected user management subsystem.
Affected software
- iot-ecology/rust-iot-platform — all versions/commits up to and including commit
5df942ab6bc46a3bf83dbee8c7970554f92c972d.
Severity
- CVSS v3.1 Base Score: 9.8 (Critical) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS v4.0 Base Score: 9.3 (Critical) —
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: No fixed release has been published for this issue as of disclosure. Track the upstream repository (iot-ecology/rust-iot-platform) for a commit or release that adds authentication guards to the affected route handlers, and upgrade to that version as soon as it is available.
- If no patch is available:
- Do not expose rust-iot-platform API endpoints, particularly the user management routes, directly to the internet or untrusted networks.
- Place the service behind a reverse proxy or API gateway that enforces authentication/authorization (e.g., mutual TLS, an external auth proxy, or an API gateway with token validation) in front of all routes until upstream request guards are implemented.
- Restrict network access to the API via firewall rules or VPN so only trusted internal hosts/administrators can reach it.
- Monitor for unexpected user creation, modification, or deletion events, and audit existing user accounts for signs of unauthorized changes.
- If feasible, add authentication middleware/guards to the
user_router.rshandlers directly in a local fork/patch before deploying to production.

