CVE-2026-59164

NORA missing cross-user token-management authorization

Published Oct 28, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

NORA is a self‑hosted artifact registry that authenticates the token‑management UI but, prior to version 0.9.5, it does not enforce administrator‑level authorization for state‑changing token operations. The middleware allows a bearer token with write rights or a write‑capable OIDC identity to call endpoints that list all tokens or revoke tokens based solely on a role.can_write() check. Consequently, any authenticated user who can write can enumerate the identifiers, owners, roles, descriptions, expiries, and last‑used timestamps of every token in the system. A bearer token possessing write privileges can also revoke arbitrary admin or service tokens, effectively disrupting the registry and forcing credential recovery. This flaw represents a Missing Permissions weakness (CWE‑862) that can lead to privilege escalation and denial of service for the registry occupant.

Affected Systems

The issue affects the getnora‑io/nora artifact registry software. Versions prior to 0.9.5 are vulnerable. The vulnerability is relevant to deployments of the self-hosted registry that expose the token‑management UI or API endpoints (e.g., /ui/tokens, /api/ui/tokens).

Risk and Exploitability

The CVSS score for this vulnerability is 7.1, indicating a medium‑high severity. EPSS is currently not available, but the flaw has not been reported as a known exploited vulnerability in the CISA KEV catalogue. The attack requires an authenticated bearer token that has write permissions or a write‑capable identity. Attackers with such credentials can enumerate all tokens and revoke privileged tokens, causing a denial of service or facilitating further credential compromise. The lack of an administrative check makes the vulnerability exploitable without needing elevated privileges beyond a standard write user.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to getnora‑io/nora version 0.9.5 or later to receive the vendor‑supplied fix.
  • If the upgrade cannot be performed immediately, restrict or disable write access to the /api/ui/tokens and /ui/tokens endpoints and enforce an administrator check for revocation operations.
  • Limit the scopes granted to bearer tokens and OIDC identities to the minimum necessary for their purpose, removing write permissions when not required.
  • Monitor registry logs for unexpected token enumeration or revocation activity and trigger alerts.

Generated by OpenCVE AI on October 28, 2026 at 15:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Getnora-io
Getnora-io nora
Vendors & Products Getnora-io
Getnora-io nora
Type Values Removed Values Added
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.
Title NORA missing cross-user token-management authorization
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 6:32 PM
Reserved
Jul 2, 2026, 4:50 PM
Status
Deferred
Published
Oct 28, 2026, 2:17 PM
Modified
Nov 4, 2026, 11:10 PM