# 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.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026

## 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
 
1. Get any valid session/API/MCP token.
2. Pick a target `login` that is a confirmed miner.
3. `GET /v1/contributors/{target}/profile` → 200 with `gittensor.hotkey`, `alphaPerDay`, `taoPerDay`, `usdPerDay`.
4. `GET /v1/contributors/{target}/decision-pack` (same token) → 403, proving the missing gate.
5. MCP `gittensory_get_contributor_profile` with `{target}` → result includes the three `*PerDay` fields.
### 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 | Ecosystem | 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.

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-382c-vx95-w3p5 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of GHSA-382c-vx95-w3p5 in the wild and no public exploit code.

Affected packages and fixed versions:
- @jsonbored/gittensory-mcp (npm): affected all versions up to 0.1.0; no fix listed
- @jsonbored/gittensory-mcp (npm): affected all versions up to 0.1.0; 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/GHSA-382c-vx95-w3p5/ (Markdown: https://insights.sbomify.com/GHSA-382c-vx95-w3p5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-382c-vx95-w3p5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-382c-vx95-w3p5/
Summaries are generated and may contain mistakes; the official description above is the record.