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

> Attackers can bypass authentication by sending any non-empty Authorization header, gaining unauthorized access to protected endpoints in the Rust IoT platform.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-82xc-gf8p-89h7

## What is CVE-2026-71277?

CVE-2026-71277 is a critical authentication bypass vulnerability in iot-ecology rust-iot-platform, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-71277?


## How do I fix CVE-2026-71277?

No fix has been published for CVE-2026-71277 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71277 being exploited?

There is no known exploitation of CVE-2026-71277 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71277 and fix it if it is affected.

What it is: CVE-2026-71277 is a critical authentication bypass vulnerability in iot-ecology rust-iot-platform, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71277 in the wild and no public exploit code.

Affected product: iot-ecology rust-iot-platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71277/ (Markdown: https://insights.sbomify.com/CVE-2026-71277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71277
- OSV: https://osv.dev/vulnerability/CVE-2026-71277

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71277/
Summaries are generated and may contain mistakes; the official description above is the record.