Skip to main content
Menu
CVEs

CVE

Teable arbitrary file write via attachment upload path traversal

Teable installs using the default local storage provider with open self-registration are exposed, and the backend container runs as root. Fixed in release.2026-07-21T11-27-40Z.2320.

CVE-2026-104100EUVD-2026-127136

Written by a model from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in release.2026-07-21T11-27-40Z.2320
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Local storage provider in use (the default) Self-registration open (the default) Backend container runs as uid 0 (root)

Published
Last modified
Reference
Last checked
17/100 · provisional
Specific setups only
1 proof of concept on GitHub

Summary

Teable, an AI spreadsheet for business, has a path traversal flaw in its attachment upload signature endpoint. A registered user can reach it remotely over the network and, when the default local storage is used, write or overwrite arbitrary files on the server. Because the backend runs as root, this can corrupt the instance or lead to root code execution.

Original description

Teable is an AI spreadsheet for business. Prior to release.2026-07-21T11-27-40Z.2320, a registered user can supply path traversal sequences in the hash field accepted by POST /api/attachments/signature when the default local storage provider is in use. In apps/nestjs-backend/src/features/attachments/plugins/local.ts, LocalStorage.presigned uses the client-controlled hash as the storage filename, and LocalStorage.save resolves that path and copies the uploaded request body without calling assertPathWithinStorage on the write path. The read path uses the jail, but the write path does not, allowing the resolved destination to escape the configured storage directory. Because the backend container runs as uid 0, the attacker can write or overwrite arbitrary root-owned files, which can corrupt the instance or lead to root code execution. Object-storage deployments that do not use LocalStorage.save are not affected by this sink. This issue is fixed in release.2026-07-21T11-27-40Z.2320.

Who should check

Teams running Teable (teableio/teable) up to 1.10.0 with the default local storage provider and open self-registration, such as standalone Docker deployments.

“teableio/teable, image ghcr.io/teableio/teable:latest , repository version 1.10.0”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Local storage provider in use (the default) Self-registration open (the default) Backend container runs as uid 0 (root)
  • Upgrade to a fixed version: release.2026-07-21T11-27-40Z.2320.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-104100 (Teable: Arbitrary root file write via attachment presign hash path traversal), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-104100 (entry last updated 2026-11-17):
Affected:
- teableio teable: fixed in release.2026-07-21T11-27-40Z.2320
Fixed versions: release.2026-07-21T11-27-40Z.2320.
Conditions (all must be true for the bug to be hit):
- Local storage provider in use (the default) (source: https://github.com/teableio/teable/security/advisories/GHSA-h4hg-45pv-pv8j)
- Self-registration open (the default) (source: https://github.com/teableio/teable/security/advisories/GHSA-h4hg-45pv-pv8j)
- Backend container runs as uid 0 (root) (source: https://github.com/teableio/teable/security/advisories/GHSA-h4hg-45pv-pv8j)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-104100 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104100 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/teableio/teable/security/advisories/GHSA-h4hg-45pv-pv8j
- https://github.com/teableio/teable/pull/3613
- https://github.com/teableio/teable/commit/cce429cb4bfc2d22732aca4835da90353f9c7fd6
- https://github.com/teableio/teable/releases/tag/release.2026-07-21T11-27-40Z.2320
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-104100
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-104100"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • teableio teable

    fixed in release.2026-07-21T11-27-40Z.2320

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-104100

Is CVE-2026-104100 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A flaw in attachment presign hash handling lets a registered user write or overwrite arbitrary files anywhere on the container filesystem as root. This can corrupt the instance or lead to remote code execution as root.Source: github.com

Which versions are affected by CVE-2026-104100?

teable: before release.2026-07-21T11-27-40Z.2320.Source: cve.now feed data

Am I affected, and how do I check?

Deployments that use the default local storage provider and have self-registration open (the default, where POST /api/auth/signup returns 201) are affected. The backend container running as uid 0 (root) is part of the impact. Check the storage provider setting, whether signup is open, and the user the backend container runs as.Source: github.com

How do I fix CVE-2026-104100?

Upgrade Teable to release.2026-07-21T11-27-40Z.2320, the fixed version listed for this vulnerability.Source: github.com

More CVEs