CVE-2026-56773
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% of all known CVEs
Summary
In Teable v2, the 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.
Risk Assessment
The organization is at risk of unauthorized data access, modification, or deletion, potentially compromising data confidentiality and integrity.
Recommendation
Immediately update Teable to a version with proper @Permissions annotations on all ORPC endpoints, or apply temporary firewall rules to block access to vulnerable endpoints.
Other vulnerabilities in Teable
See all- CVE-2026-56781Medium
A vulnerability in Teable before 2026-06-15T04-43-24Z.1912 allows anonymous attackers to access hidden field data by supplying arbitrary field IDs in the projection parameter of the share view records endpoint. Attackers can read field values that are intended to be restricted from public view.
- CVE-2026-9566Medium
In teableio teable up to version 1.9.x, the Sign-up component in apps/nextjs-app/src/features/auth/pages/LoginPage.tsx is vulnerable to cross site scripting via the redirect argument. The attack is remotely exploitable and the exploit is publicly available.
Original NVD description (English 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.