{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-59164","id":"CVE-2026-59164","title":"NORA token data exposure in token-management UI","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_t","descriptionLong":"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.","published":"2026-10-28T13:05:47.302Z","updated":"2026-11-05T21:16:10.362068584Z","reserved":"2026-07-02T16:50:27.887Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"GitHub_M"},"metrics":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"GitHub_M"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"github.com"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"OSV"}],"rating":"high","products":["getnora-io nora"],"affectedProducts":[{"vendor":"getnora-io","product":"nora","defaultStatus":null,"versions":[{"version":"< 0.9.5","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-862"],"aliases":["GHSA-78cx-cfhm-rgmx"],"references":[{"url":"https://github.com/getnora-io/nora/security/advisories/GHSA-78cx-cfhm-rgmx","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/getnora-io/nora/pull/747","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/getnora-io/nora/commit/dc9e943b208095ec1e8cc2cf7b5108fdb55cab9c","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/getnora-io/nora/releases/tag/v0.9.5","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/59xxx/CVE-2026-59164.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-59164","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial"},"epss":0.00199,"epssPercentile":0.09887,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-59164","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-59164","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-59164","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-59164","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}