CVE-2026-104100

Teable: Arbitrary root file write via attachment presign hash path traversal

Published Nov 17, 2026 CVSS 3.1 · 8.8 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Teable, an AI spreadsheet application, has a path traversal flaw in the attachment presign hash creation endpoint. The backend’s LocalStorage.presigned routine accepts a client‑controlled hash as a filename and creates a presigned URL without validating the resulting write path. An attacker can supply hash values containing directory traversal sequences, causing the server to copy uploaded data to arbitrary locations under the container’s root filesystem. Because the container runs as uid 0, the attacker can overwrite or create any file on the host, leading to system corruption or root code execution. The weakness is a combination of improper input validation (CWE‑20) and path traversal (CWE‑22), and it allows complete compromise of confidentiality, integrity, and availability.

Affected Systems

The vulnerability affects all deployments of Teable prior to release.2026-07-21T11-27-40Z.2320 that use the default local storage provider. Object‑storage configurations that do not invoke LocalStorage.save are not impacted.

Risk and Exploitability

With a CVSS score of 8.8 the flaw is considered high severity. EPSS data are not available, and the vulnerability is not listed in the CISA KEV catalog, so the precise exploitation likelihood cannot be quantified. Nevertheless, the attack path is straightforward: an authenticated user can craft a malicious hash and request a presigned URL; the backend writes the payload to a location controlled by the attacker. Running as root amplifies the impact, making this a top‑priority risk for affected environments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Teable to release.2026-07-21T11-27-40Z.2320, which contains the fix for the path traversal issue.
  • If an upgrade is not immediately feasible, reconfigure the backend to use an object storage provider that does not employ LocalStorage.save, or disable the attachment presign hash feature to eliminate the vulnerable write path.
  • Ensure that the backend container does not run with root privileges; running as a non‑root user limits the impact of any remaining write vulnerabilities.

Generated by OpenCVE AI on November 17, 2026 at 19:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title Teable: Arbitrary root file write via attachment presign hash path traversal
Weaknesses CWE-20
CWE-22
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Subscriptions

No data.

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 17, 2026, 5:49 PM
Reserved
Oct 1, 2026, 6:05 PM
Status
Received
Published
Nov 17, 2026, 6:17 PM
Modified
Nov 17, 2026, 6:17 PM