Skip to main content
← All vulnerabilities
CVE-2026-59164EUVD-2026-112076GHSA-78CX-CFHM-RGMX

NORA missing cross-user token-management authorization

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 0.9.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

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.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • getnora-io nora

    fixed in 0.9.5

References 4

GitHub · getnora-io/nora