CVE-2026-104100

Teable attachment paths could overwrite files outside storage

teableio · Teable AI workflow and database platform

First documented disclosure · Review checkpoint

Summary

A registered user could choose an attachment destination outside the storage directory.

Severity and exploitation evidence

High · 8.8/10 · CVSS 3.1. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed sources.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The upload path used a client-supplied hash without enforcing filesystem containment.

Conditions required

The installation uses local attachment storage and the attacker has a registered account. The documented container runs as root.

Potential impact

Files in the backend container can be overwritten, potentially enabling code execution with its privileges.

Affected versions and configurations

Before release.2026-07-21T11-27-40Z.2320, according to the CNA.

Fix and mitigation status

release.2026-07-21T11-27-40Z.2320, according to the CNA.

Practical next steps

Deploy the CNA-identified corrected release or later and restrict backend filesystem privileges. Object-storage deployments do not use the affected local write path.

Operating lesson

Generate attachment filenames on the server and enforce storage containment.

Evidence and limits

The public correction PR opened July 18 and explicitly lists the attachment path-traversal security fix; it merged July 21. The detailed GitHub advisory followed August 26 and CVE publication November 17. Its package table lists an earlier corrected build, release.2026-07-20T11-53-25Z.2296; this row uses the later CNA-confirmed release. The first fixed build remains uncertain. Scope is the platform’s shared backend, not model behavior.

Sources