# CVE-2026-108747: Lightdash through 2.556.0 Authorization Bypass via Personal Access Token Deletion

> Authenticated users can delete other users' personal access tokens across organizations, disrupting API integrations and requiring an upgrade to fix.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-7xvq-pcf6-2w3w

## What is CVE-2026-108747?

CVE-2026-108747 is a low-severity missing authorization vulnerability in lightdash, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lightdash through 2.556.0 contains an authorization bypass vulnerability that allows authenticated organization members to delete other users' personal access tokens by supplying their UUID. Attackers can send DELETE requests to the personal-access-tokens route with a victim's token UUID, even across organizations, to revoke it and break API integrations.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-108747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108747 is a low-severity missing authorization vulnerability in lightdash, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108747 in the wild and no public exploit code.

Affected product: lightdash. 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-108747/ (Markdown: https://insights.sbomify.com/CVE-2026-108747/index.md)
```

## Sources

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

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