# CVE-2026-129127: SQLBot through 1.10.3 Weak Password Hashing via Unsalted MD5


- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-p33h-chx9-f9hf

## What is CVE-2026-129127?

CVE-2026-129127 is a medium-severity vulnerability in dataease SQLBot, published on 13 Nov 2026. 

### Official description

SQLBot through 1.10.3 contains a weak password hashing vulnerability that stores local account passwords in sys_user.password as unsalted MD5 digests via md5pwd() in security.py. Attackers who obtain the user table can recover passwords, including administrator passwords, using precomputed tables or GPU cracking, since identical passwords produce identical hashes.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

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

1 open source package ship an affected version, including dataease/sqlbot.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dataease/sqlbot` | GitHub | `pkg:github/dataease/sqlbot` | All versions to 1.10.3 | None |

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

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

## Is CVE-2026-129127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129127 is a medium-severity vulnerability in dataease SQLBot, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129127 in the wild and no public exploit code.

Affected packages and fixed versions:
- dataease/sqlbot (GitHub): affected all versions up to 1.10.3; no fix listed

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

## Sources

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

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