# CVE-2026-110770: Databasus 3.7.0 through 3.61.0 Account Takeover via Password Reset Brute-Force

> Unauthenticated attackers can brute-force password reset codes to take over user accounts, including administrators, due to missing rate limiting.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-jj5w-98p7-g6gj

## What is CVE-2026-110770?

CVE-2026-110770 is a critical authentication bypass vulnerability in databasus, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Databasus 3.7.0 through 3.61.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to brute-force password reset codes via POST /api/v1/users/reset-password. Attackers can request a six-digit code for a known email, then guess it without rate limiting, lockout, or invalidation to take over accounts, including administrators.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-110770 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110770 is a critical authentication bypass vulnerability in databasus, published on 14 Oct 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-110770 in the wild and no public exploit code.

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

## Sources

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

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