CVE-2026-59164 NORA missing cross-user token-management authorization
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
1 package: 0 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| getnora-io nora | = < 0.9.5 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| getnora-io nora | = < 0.9.5 | No fix listed |
References
- https://github.com/getnora-io/nora/security/advisories/GHSA-78cx-cfhm-rgmx exploit
- 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
- ENISA EUVD EUVD-2026-112076 third-party-advisory