CVE-2026-59164
Published:October 28, 2026
Updated:October 30, 2026
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.
Affected Packages
https://github.com/getnora-io/nora.git (GITHUB):
Affected version(s) >=v0.2.1 <v0.9.5Fix Suggestion:
Update to version v0.9.5nora-registry (RUST):
Affected version(s) =0.2.35 <1.2.0Fix Suggestion:
Update to version 1.2.0Related Resources (4)
Do you need more information?
Contact UsCVSS v4
Base Score:
7.1
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
LOW
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
7.1
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Missing Authorization
EPSS
Base Score:
0.20