Skip to main content
VulnerabilityPublished

CVE-2026-104100: teableio teable · Improper Input Validation

Affects teableio teableSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 17 Nov 2026, 18:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
teableioteableAffected
  • =< release.2026-07-21T11-27-40Z.2320
Fixed in–

AI-suggested

A fix is available in teable release.2026-07-21T11-27-40Z.2320. Users should upgrade to this version to remediate the vulnerability. Deployments using object storage instead of the default local storage provider are not affected by this issue. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-104100 is an improper input validation vulnerability in teableio's teable AI spreadsheet product. A registered user can exploit a path traversal flaw in the POST /api/attachments/signature endpoint when the default local storage provider is used. This allows writing files outside the intended storage directory because the write path does not enforce path restrictions. Since the backend container runs as root, this can lead to arbitrary root-owned file overwrite, potentially causing instance corruption or root code execution. The issue is fixed in release.2026-07-21T11-27-40Z.2320.

References

Community reviews

Loading reviews…