Skip to main content
Menu
CVEs

CVE

Teable cross-tenant access bypass in child-resource lookups

CVE-2026-86061EUVD-2026-127137

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-17T05-20-38Z.2264
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Teable versions before release.2026-07-17T05-20-38Z.2264

Published
Last modified
Reference
Last checked
17/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Teable, an AI spreadsheet for business, has access control flaws that let a logged-in attacker reach other tenants' resources remotely, with no user action needed. An attacker can view or change other tenants' views, filters, and plugin storage, rotate and reveal another plugin's OAuth secret, or delete plugins, including system plugins.

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

Original description

Teable is an AI spreadsheet for business. Prior to release.2026-07-17T05-20-38Z.2264, the routes for PluginService::regenerateSecret and PluginService::delete carry no @Permissions decorator, and the methods omit plugin ownership checks. An authenticated attacker can directly target another plugin's identifier to rotate and disclose its OAuth secret or delete the plugin, including system plugins. Separately, PermissionGuard authorizes several nested API requests using a caller-controlled parent tableId, baseId, or spaceId, while the services resolve the requested child object only by its globally unique identifier. An authenticated attacker can provide a parent resource the attacker owns together with a victim's child identifier. ViewService::getViewById can then disclose another tenant's view configuration, embedded filter values, field layout, and shareId. DashboardService::updatePluginStorage and the view-position updatePluginStorage path can overwrite another tenant's plugin storage because the plugin installation is not rebound to the authorized base, dashboard, table, or view. This issue is fixed in release.2026-07-17T05-20-38Z.2264.

Who should check

Teams running self-hosted or multi-tenant Teable (teableio/teable) builds older than release.2026-07-17T05-20-38Z.2264, including instances with plugins or shared bases and views.

“< release.2026-07-17T05-20-38Z.2264”

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.

    Teable versions before release.2026-07-17T05-20-38Z.2264
  • Upgrade to a fixed version: release.2026-07-17T05-20-38Z.2264.

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-86061 (Teable: child-resource lookups permit cross-tenant data access and modification), 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-86061 (entry last updated 2026-11-17):
Affected:
- teableio teable: fixed in release.2026-07-17T05-20-38Z.2264
Fixed versions: release.2026-07-17T05-20-38Z.2264.
Conditions (all must be true for the bug to be hit):
- Teable versions before release.2026-07-17T05-20-38Z.2264 (source: https://github.com/teableio/teable/security/advisories/GHSA-7xph-fchg-qpwf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-86061 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86061 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-7xph-fchg-qpwf
- https://github.com/teableio/teable/commit/52c387e49ae88218cadc81cd0209653742b8add8
- https://github.com/teableio/teable/releases/tag/release.2026-07-17T05-20-38Z.2264
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-86061
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-86061"}.

Timeline

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

Affected versions

  • teableio teable

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

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

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

Questions about CVE-2026-86061

Is CVE-2026-86061 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?

Authenticated users can act on child resources belonging to other tenants. They can delete any plugin, rotate and capture any plugin's OAuth client secret, read other tenants' view configuration including filter values and shareId, and overwrite other tenants' dashboard and view plugin storage.Source: github.com, github.com

Which versions are affected by CVE-2026-86061?

teable: before release.2026-07-17T05-20-38Z.2264.Source: cve.now feed data

Am I affected, and how do I check?

Teable versions before release.2026-07-17T05-20-38Z.2264 are affected. To check your version, look at the release identifier of your Teable installation.Source: github.com, github.com

How do I fix CVE-2026-86061?

Upgrade Teable to release.2026-07-17T05-20-38Z.2264 or later, which is the listed fixed version.Source: github.com, github.com

More CVEs