# CVE-2026-59164: NORA missing cross-user token-management authorization


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-78cx-cfhm-rgmx

## What is CVE-2026-59164?

CVE-2026-59164 is a high-severity vulnerability in getnora-io nora, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-59164?


## How do I fix CVE-2026-59164?

No fix has been published for CVE-2026-59164 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59164 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59164 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59164 and fix it if it is affected.

What it is: CVE-2026-59164 is a high-severity vulnerability in getnora-io nora, published on 28 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59164 exists.

Affected product: getnora-io nora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59164/ (Markdown: https://insights.sbomify.com/CVE-2026-59164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59164
- OSV: https://osv.dev/vulnerability/CVE-2026-59164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59164/
Summaries are generated and may contain mistakes; the official description above is the record.