# CVE-2026-112004: Teable before 2026-10-12T12-45-53Z.3331 Authorization Bypass via Folder Rename Endpoint

> Authenticated attackers can rename folders in bases they do not belong to by exploiting an authorization bypass in the folder rename endpoint.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 18 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-5qj3-rq3x-q739, GHSA-f2vw-v2g4-6v2v

## What is CVE-2026-112004?

CVE-2026-112004 is a low-severity missing authorization vulnerability in teableio teable, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Teable before 2026-10-12T12-45-53Z.3331 contains an authorization bypass vulnerability that allows authenticated users to rename folders in other bases by supplying a foreign folderId. The PATCH /api/base/:baseId/node/folder/:folderId endpoint checks base|update only against the URL baseId, so attackers can rename folders in bases where they lack membership.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-112004 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112004 is a low-severity missing authorization vulnerability in teableio teable, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112004 exists.

Affected product: teableio teable. 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-112004/ (Markdown: https://insights.sbomify.com/CVE-2026-112004/index.md)
```

## Sources

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

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