CVE-2026-71277 json
rust-iot-platform Authentication Bypass via Non-Validated Authorization Header
published 2026-08-05 3 mo ago modified 2026-10-23 16 d ago also EUVD-2026-53362
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- iot-ecology rust-iot-platform
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/iot-ecology/rust-iot-platform
third-party-advisory
-
github.com
/iot-ecology/rust-iot-platform/blob/main/api/src/main.rs
third-party-advisory
Sources
- CVE List CVE-2026-71277
- NVD CVE-2026-71277
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.