GHSA-382c-vx95-w3p5 Gittensory: Missing contributor-scoped access control on profile endpoint and MCP tool leaks miner financial data
Authenticated users can access other contributors' financial data and hotkeys due to missing access control checks on the profile endpoint.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is GHSA-382c-vx95-w3p5?
GHSA-382c-vx95-w3p5 is a missing authorization vulnerability in @jsonbored/gittensory-mcp, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Summary
GET /v1/contributors/:login/profile and the gittensory_get_contributor_profile MCP tool skip the contributor-scoped access check that every sibling endpoint enforces. Any authenticated session/API/MCP token holder can read any contributor's profile; for confirmed Gittensor miners that exposes alphaPerDay, taoPerDay, usdPerDay (and the hotkey on the REST path). Authenticated cross-contributor disclosure, CWE-284 / IDOR.
Details
In src/api/routes.ts the profile handler returns buildContributorProfile(...) with no requireContributorAccess call. Every sibling (/decision-pack, /repos/:owner/:repo/decision, etc.) gates and 403s on a cross-contributor request — the profile route is the only omission. buildContributorProfile (src/signals/engine.ts) embeds hotkey and the three *PerDay fields for any confirmed miner.
The MCP tool getContributorProfile (src/mcp/server.ts) also omits requireContributorAccess. Its redactSensitiveForMcp filter only strips keys matching hotkey|coldkey|wallet|private_key|privateKey|mnemonic, so the hotkey is dropped but alphaPerDay/taoPerDay/usdPerDay pass through.
The codebase treats these as secret everywhere else — decision-pack.ts destructures the hotkey out before serving, and three sanitizers scrub hotkey/wallet from AI/comment output — which is why this is an oversight, not by-design.
Exposure: REST → hotkey + 3 financial fields; MCP → 3 financial fields (hotkey redacted).
PoC
- Get any valid session/API/MCP token.
- Pick a target
loginthat is a confirmed miner. GET /v1/contributors/{target}/profile→ 200 withgittensor.hotkey,alphaPerDay,taoPerDay,usdPerDay.GET /v1/contributors/{target}/decision-pack(same token) → 403, proving the missing gate.- MCP
gittensory_get_contributor_profilewith{target}→ result includes the three*PerDayfields.
Impact
Any token holder can enumerate other miners' daily TAO/alpha/USD revenue (plus hotkey via REST) without authorization. All miners with snapshot data are affected.
Which versions are affected by GHSA-382c-vx95-w3p5?
2 open source packages ship an affected version, including @jsonbored/gittensory-mcp.
| Package | Affected | Fixed in |
|---|---|---|
@jsonbored/gittensory-mcp npm | All versions to 0.1.0 | None |
@jsonbored/gittensory-mcp npm | All versions to 0.1.0 | None |
How do I fix GHSA-382c-vx95-w3p5?
No fix has been published for GHSA-382c-vx95-w3p5 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is GHSA-382c-vx95-w3p5 being exploited?
There is no known exploitation of GHSA-382c-vx95-w3p5 in the wild and no public exploit code.