CVE-2026-59164

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.

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.

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.

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.