# CVE-2026-84485: APITable through 1.13.0-beta.1 Missing Authentication on the Internal Organization Load or Search Endpoint

> Unauthenticated attackers can access the internal organization load or search endpoint to enumerate member names, emails, and team hierarchies in APITable workspaces.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** 2 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-mmm8-g668-9442

## What is CVE-2026-84485?

CVE-2026-84485 is a high-severity missing authorization vulnerability in apitable, published on 2 Sep 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 exposes the internal organization loadOrSearch endpoint without authentication, allowing unauthenticated attackers to retrieve member names, email addresses, and team hierarchy. Attackers can query the endpoint with space identifiers obtained from shared links or public templates to enumerate the complete member directory of any workspace.

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

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


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

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

## Is CVE-2026-84485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84485 is a high-severity missing authorization vulnerability in apitable, published on 2 Sep 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-84485 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-84485/ (Markdown: https://insights.sbomify.com/CVE-2026-84485/index.md)
```

## Sources

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

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