CVE-2026-86061

Teable nested resource checks could expose other tenants’ data and plugin secrets

teableio · Teable AI workflow and database platform

First documented disclosure · Review checkpoint

Summary

A signed-in user could target another tenant’s plugin or nested resources.

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

Some handlers omitted ownership checks or authorized a parent resource while resolving an unrelated child by its identifier.

Conditions required

The attacker has an account and can identify the targeted resource.

Potential impact

Plugin secrets and view configuration can be disclosed; plugins can be deleted and plugin storage modified across tenants.

Affected versions and configurations

Before release.2026-07-17T05-20-38Z.2264.

Fix and mitigation status

release.2026-07-17T05-20-38Z.2264.

Practical next steps

Upgrade to the corrected release or later, rotate exposed plugin secrets, and review cross-tenant changes.

Operating lesson

Bind every nested object to the resource authorized for the request.

Evidence and limits

The public correction PR opened July 16 and explicitly lists plugin authorization and scope-boundary hardening. Its merged commit adds ownership and parent-resource checks to the affected handlers. The detailed GitHub advisory followed October 13 and CVE publication November 17. Scope is shared infrastructure of Teable’s integrated AI chat, agent, workflow and database platform.

Sources