# CVE-2026-95654: Databasement before 1.7.14 Authorization Bypass via Stale Invitation Token

> Attackers can hijack accounts and access database secrets by exploiting stale invitation tokens in Databasement.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-9cq7-qg25-29v5

## What is CVE-2026-95654?

CVE-2026-95654 is a critical authentication bypass vulnerability in David-Crty Databasement, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Databasement before 1.7.14 validates invitation tokens only when the acceptance page loads, caching the authorization decision without re-checking token validity during acceptance. Attackers with a leaked or forwarded invitation link can load the page while pending, then accept the invitation after the legitimate user has already accepted it to overwrite the account password and gain authenticated access to managed database credentials and secrets.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-95654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95654 is a critical authentication bypass vulnerability in David-Crty Databasement, published on 22 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-95654 in the wild and no public exploit code.

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

## Sources

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

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