# CVE-2026-80208: APITable through 1.13.0-beta.1 Missing Authentication on the Internal Account Closure Endpoints

> Unauthenticated attackers can permanently close user accounts and delete associated data by accessing internal endpoints that lack authentication checks.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-84jw-g3q8-wfgq

## What is CVE-2026-80208?

CVE-2026-80208 is a high-severity missing authorization vulnerability in apitable, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

APITable through 1.13.0-beta.1 annotates both getUserHistories and closePausedUserAccount in InternalUserController with requiredLogin = false. ResourceInterceptor honours that annotation by returning before any session or API key is validated, and the nginx gateway shipped with the product proxies every /api request to the backend server, so both endpoints are reachable by any unauthenticated client that can reach the gateway. An attacker can POST to /api/v1/internal/getUserHistories to enumerate the accounts sitting in the 30-day cooling-off period that follows a deletion request, then POST to /api/v1/internal/users/{userId}/close for each one. The closure path clears the account's email address, phone number and nickname, cancels its space subscriptions, removes its space memberships and deletes its OAuth bindings, so the cooling-off window that exists to let a user reverse a deletion request is bypassed and the account cannot be recovered.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-80208?


## How do I fix CVE-2026-80208?

No fix has been published for CVE-2026-80208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80208 being exploited?

There is no known exploitation of CVE-2026-80208 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80208 and fix it if it is affected.

What it is: CVE-2026-80208 is a high-severity missing authorization vulnerability in apitable, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80208 in the wild and no public exploit code.

Affected product: apitable. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80208/ (Markdown: https://insights.sbomify.com/CVE-2026-80208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80208
- OSV: https://osv.dev/vulnerability/CVE-2026-80208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80208/
Summaries are generated and may contain mistakes; the official description above is the record.