# REBUILD: an MCP tool hands an ordinary account the admin password hash

> CVE-2026-129875 turns REBUILD's MCP QueryRecords tool into an oracle that leaks the administrator's password hash character by character.

- **Severity:** Medium: Real and reproducible, but needs unusual setup, user help or a narrow audience. Plan a fix.
- **Category:** Vulnerability
- **Published by:** VulnCheck
- **Disclosed:** 2026-11-16
- **CVE:** CVE-2026-129875
- **CVSS:** 8.7
- **Affects:** REBUILD
- **Research by:** Wu Yulun
- **Primary source:** https://www.vulncheck.com/advisories/rebuild-4.5.0-through-4.5.4-password-hash-disclosure-via-mcp-queryrecords
- **Page:** https://theinjection.dev/items/rebuild-mcp-queryrecords-admin-hash/

CVE-2026-129875 lets a low-privileged REBUILD user read the administrator's SHA-256 password hash through the platform's MCP QueryRecords tool, then sign in as admin. VulnCheck published it with three more REBUILD flaws.

## What happened

VulnCheck published CVE-2026-129875 against REBUILD on November 16, 2026, crediting Wu Yulun. REBUILD is an open-source business platform whose 4.5.0 release added MCP support, so external AI clients can call its tools. Three more REBUILD flaws received CVEs the same day, and the project shipped 4.5.5 on November 16.

## How it works

A blind prefix-match oracle is the mechanism. REBUILD's MCP QueryRecords tool accepts a filter on the User.password field and returns a total row count. The reported technique sends LK2 prefix-match filters to the /gw/mcp/sse gateway and reads the returned count to confirm the stored SHA-256 hash one character at a time. REBUILD accepts that hash as a login credential, so recovering it is enough to sign in as administrator.

## Who is affected

REBUILD 4.5.0 through 4.5.4 carry the MCP flaw, since MCP support arrived in 4.5.0. The other three CVEs reach further back, as far as 2.7.0, and are listed below. An ordinary authenticated account on the instance is enough, so deployments that give accounts to untrusted users are the ones at risk.

## What to do

Upgrade to REBUILD 4.5.5, which sits outside the version range VulnCheck lists as affected. Rotate administrator passwords afterwards, because the flaw exposes the stored hash and REBUILD accepts a hash as a credential. Restrict who can reach the /gw/mcp/sse gateway and review which users hold the personal keys REBUILD issues for external MCP clients.

## Quick facts

- **Affected:** REBUILD 4.5.0 through 4.5.4 for the MCP flaw
- **Fixed in:** 4.5.5, released November 16, 2026; its notes name no security fix
- **CVE:** CVE-2026-129875, CVSS 4.0 base score 8.7, rated high by VulnCheck
- **Other CVEs:** CVE-2026-129874 role self-escalation (3.5.0 to 4.5.4), CVE-2026-129873 SYSTEM_USER token (4.3.0 to 4.5.4), CVE-2026-129872 SQL injection (2.7.0 to 4.5.4)
- **Found by:** Wu Yulun
- **Disclosed:** Write-up dated November 6, 2026; CVEs published November 16, 2026
- **Attack type:** Blind prefix-match oracle through an MCP tool filter

## Questions

### Which REBUILD version fixes CVE-2026-129875?

VulnCheck lists REBUILD 4.5.0 through 4.5.4 as affected by CVE-2026-129875, which places 4.5.5 outside the affected range. REBUILD released 4.5.5 on November 16, 2026, the same day the CVEs appeared, and its release note says only that it fixes several known issues. Neither that note nor the V4.5 changelog names the four flaws.

### Do I need to rotate REBUILD administrator passwords after upgrading?

Rotating REBUILD administrator passwords is the prudent step, because CVE-2026-129875 exposes the stored SHA-256 hash and REBUILD accepts that hash as a login credential. An attacker who extracted a hash before the upgrade keeps a working admin credential until the password changes. VulnCheck's advisory states no rotation requirement, so treat this as a consequence of the flaw.

### Does the REBUILD MCP flaw need administrator access to exploit?

An ordinary authenticated REBUILD account is enough for CVE-2026-129875, and administrator rights are not needed. VulnCheck's CVSS 4.0 vector records low privileges required and a network attack vector, with no user interaction. The write-up names an ordinary account as the starting point for three of the four flaws, which puts any REBUILD deployment with untrusted users in scope.

## Sources

1. [VulnCheck Advisory](https://www.vulncheck.com/advisories/rebuild-4.5.0-through-4.5.4-password-hash-disclosure-via-mcp-queryrecords)
2. [GitHub Advisory](https://github.com/advisories/GHSA-r24j-jphp-67xq)
3. [Researcher Write-Up](https://vul.yulun.ac.cn/20261106/rebuild)
4. [REBUILD 4.5.5 Release](https://github.com/getrebuild/rebuild/releases/tag/4.5.5)
