Gittensory: Missing contributor-scoped access control on profile endpoint and MCP tool leaks miner financial data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary GET /v1/contributors/:login/profile and the gittensorygetcontributorprofile 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…

Published by the source

9 Jul 2026, 13:44 UTC

Last modified by the source

9 Jul 2026, 14:00 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-382c-vx95-w3p5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-382c-vx95-w3p5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-382c-vx95-w3p5

Advisory: Gittensory: Missing contributor-scoped access control on profile endpoint and MCP tool leaks miner financial data
IDs: GHSA-382c-vx95-w3p5
Record: https://patchnext.com/advisories/ghsa-382c-vx95-w3p5 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @jsonbored/gittensory-mcp: affected <= 0.1.0

## Suggested inspection (read-only)
- `npm ls @jsonbored/gittensory-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @jsonbored/gittensory-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-382c-vx95-w3p5 (OSV record GHSA-382c-vx95-w3p5 lists affected ranges: npm @jsonbored/gittensory-mcp >=0 <=0.1.0)
- Verified: https://github.com/advisories/GHSA-382c-vx95-w3p5 (GitHub-reviewed advisory GHSA-382c-vx95-w3p5 lists affected ranges: npm @jsonbored/gittensory-mcp >=0 <=0.1.0)

Commands are suggestions: review each one before running it.