What is GHSA-382C-VX95-W3P5?

GHSA-382C-VX95-W3P5 is a medium-severity security vulnerability in @jsonbored/gittensory-mcp (npm), affecting versions <= 0.1.0. No fixed version is listed yet.

How severe is GHSA-382C-VX95-W3P5?

GHSA-382C-VX95-W3P5 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @jsonbored/gittensory-mcp are affected by GHSA-382C-VX95-W3P5?

@jsonbored/gittensory-mcp (npm) versions <= 0.1.0 is affected.

Is there a fix for GHSA-382C-VX95-W3P5?

No fixed version is listed for GHSA-382C-VX95-W3P5 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-382C-VX95-W3P5 exploitable, and should I be worried?

Whether GHSA-382C-VX95-W3P5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-382C-VX95-W3P5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-382C-VX95-W3P5 in @jsonbored/gittensory-mcp

Q: How severe is GHSA-382C-VX95-W3P5?

GHSA-382C-VX95-W3P5 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @jsonbored/gittensory-mcp are affected by GHSA-382C-VX95-W3P5?

@jsonbored/gittensory-mcp (npm) versions <= 0.1.0 is affected.

Q: Is there a fix for GHSA-382C-VX95-W3P5?

No fixed version is listed for GHSA-382C-VX95-W3P5 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-382C-VX95-W3P5 exploitable, and should I be worried?

Whether GHSA-382C-VX95-W3P5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-382C-VX95-W3P5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

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

Full technical description

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 login that is a confirmed miner.
GET /v1/contributors/{target}/profile → 200 with gittensor.hotkey, alphaPerDay, taoPerDay, usdPerDay.
GET /v1/contributors/{target}/decision-pack (same token) → 403, proving the missing gate.
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.

GHSA-382C-VX95-W3P5 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

@jsonbored/gittensory-mcp (<= 0.1.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for GHSA-382C-VX95-W3P5 yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-382C-VX95-W3P5? GHSA-382C-VX95-W3P5 is a medium-severity security vulnerability in @jsonbored/gittensory-mcp (npm), affecting versions <= 0.1.0. No fixed version is listed yet.
How severe is GHSA-382C-VX95-W3P5? GHSA-382C-VX95-W3P5 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @jsonbored/gittensory-mcp are affected by GHSA-382C-VX95-W3P5? @jsonbored/gittensory-mcp (npm) versions <= 0.1.0 is affected.
Is there a fix for GHSA-382C-VX95-W3P5? No fixed version is listed for GHSA-382C-VX95-W3P5 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-382C-VX95-W3P5 exploitable, and should I be worried? Whether GHSA-382C-VX95-W3P5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-382C-VX95-W3P5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.