# CVE-2026-47697: Missing authorization in shelf.nu

> Authenticated users can access or modify other organizations' asset data due to missing tenant isolation checks in Shelf.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-r46p-gfrp-xxgq

## What is CVE-2026-47697?

CVE-2026-47697 is a high-severity missing authorization vulnerability in Shelf-nu shelf.nu, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Shelf is a platform for tracking physical assets. Shelf is multi-tenant; data is isolated per organization (workspace). Prior to version 1.20.2, several endpoints accepted entity IDs from request input and `connect`-ed / read / updated them without verifying the IDs belonged to the caller's organization. An authenticated user in Org A who knew or obtained an ID belonging to Org B could act on Org B's data across organization boundaries (a cross-tenant IDOR). A loader-only restriction on personal-workspace bookings was also bypassable via a crafted POST. Version 1.20.2 patches the issue. No known workarounds are available.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-47697 being exploited?

There is no known exploitation of CVE-2026-47697 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47697 is a high-severity missing authorization vulnerability in Shelf-nu shelf.nu, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47697 in the wild and no public exploit code.

Affected product: Shelf-nu shelf.nu. 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-47697/ (Markdown: https://insights.sbomify.com/CVE-2026-47697/index.md)
```

## Sources

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

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