Vulnerability in Teable (CVE-2026-56773)
Summary
Vulnerability in Teable (CVE-2026-56773). Successful exploitation can lead to full system takeover. Exploitable via GET /api/v2/tables/get.
Original description
The description as published by the source.
Teable's v2 REST API controller lacks @Permissions metadata on ORPC endpoints, allowing any authenticated user to bypass authorization checks. Attackers can read table schemas, create tables, and modify or delete records across bases and tables via endpoints like GET /api/v2/tables/get and POST /api/v2/tables/updateRecords.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-56773 has been found in Teable.
Attackers can target a specific entry point like GET /api/v2/tables/get over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Teable CVE-2026-56773" on the vendor's site.
CVE-2026-56773 (Teable) — CWE-862 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v2/tables/get / POST /api/v2/tables/updateRecords.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Teable. Attackers reach the vulnerable code path via GET /api/v2/tables/get.
Check the vendor advisory for the affected versions of Teable. Attack surface: GET /api/v2/tables/get / POST /api/v2/tables/updateRecords..
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v2/tables/get requests with malformed payloads or SQL meta-characters. Run grep -r 'Teable' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Teable' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Teableを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v2/tables/get' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2/tables/getへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v2/tables/get on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- package github.com
- report github.com
- web github.com