CVE-2026-80208 apitable CVE debrief

Who should care

Defenders responsible for APITable instances, particularly those with exposed /api endpoints, should assess exposure and apply patches or additional security measures to prevent data loss.

Why it matters

CVE-2026-80208 is a high-severity vulnerability in APITable that allows unauthenticated clients to bypass the 30-day cooling-off period after a user deletion request, leading to permanent account deletion and data loss. Defenders responsible for APITable instances should assess exposure and apply patches or additional security measures to prevent data loss.

• Data loss due to permanent account deletion
• Bypassing of 30-day cooling-off period after user deletion
• Potential for enumeration of accounts in cooling-off period
• Verification of exposure and patch application required

Technical summary

The vulnerability is caused by the InternalUserController annotating getUserHistories and closePausedUserAccount with requiredLogin = false, allowing unauthenticated access. The nginx gateway proxies /api requests to the backend server, making these endpoints reachable by any client that can reach the gateway. An attacker can use this vulnerability to enumerate accounts in the 30-day cooling-off period and permanently delete them.

Defensive priority

Defenders should prioritize verifying exposure and applying patches due to the high severity and potential for data loss.

Recommended defensive actions

• Verify exposure by checking if the APITable instance is vulnerable to unauthenticated access to /api/v1/internal/getUserHistories and /api/v1/internal/users/{userId}/close endpoints.
• Apply patches or updates to APITable to fix the vulnerability.
• Monitor for suspicious activity on the APITable instance, particularly related to user deletion and account closure.
• Implement additional security measures, such as IP restrictions or authentication mechanisms, to protect the APITable instance.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability is caused by the InternalUserController annotating getUserHistories and closePausedUserAccount with requiredLogin = false, allowing unauthenticated access. The nginx gateway proxies /api requests to the backend server, making these endpoints reachable by any client that can reach the gateway.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.