Summary
A fresh npm install of solana-agent-kit@2.0.10 reports 13 vulnerabilities (7 moderate, 6 high) via npm audit. These come from transitive dependencies and are not fixable by downstream consumers.
HIGH (6)
bigint-buffer@1.1.5 - Buffer overflow via toBigIntLE() (GHSA-3gc7-fjrx-p6mg)
- Chain:
@solana/spl-token > @solana/buffer-layout-utils > bigint-buffer
langsmith@0.3.87 - 4 advisories: SSRF (GHSA-v34v-rq6j-cj6p), prototype pollution (GHSA-fw9q-39r9-c252), streaming redaction bypass (GHSA-rr7j-v2q5-chgv), untrusted manifest deserialization (GHSA-3644-q5cj-c5c7)
- Chain:
@langchain/core@0.3.80 > langsmith@0.3.87
- Note:
langsmith@0.7.2 (latest) has fixed all 4. @langchain/core@1.1.48 also drops the vulnerable uuid dep. Bumping @langchain/core from 0.3.x to 1.x would resolve these.
MODERATE (7)
- uuid@8.3.2 via
jayson@4.3.0 (jayson latest still pins uuid@^8) - missing buffer bounds check
- uuid@10.0.0 via
@langchain/core@0.3.80 / langsmith@0.3.87 - same vuln
- ai (Vercel SDK) - filetype whitelist bypass
- jsondiffpatch - XSS via HtmlFormatter
Context
We maintain a SAK plugin (piquesignal-solana-agent-plugin) and ran a full audit before our public launch. None of these vulns are reachable from our plugin code, but they show up for every consumer running npm audit, which creates friction for adoption.
Not a demand for immediate action, just flagging for visibility. Happy to help test if patches land.
Environment
- solana-agent-kit: 2.0.10
- Node: v24.11.0
- npm: 11.6.1
Summary
A fresh
npm installofsolana-agent-kit@2.0.10reports 13 vulnerabilities (7 moderate, 6 high) vianpm audit. These come from transitive dependencies and are not fixable by downstream consumers.HIGH (6)
bigint-buffer@1.1.5 - Buffer overflow via
toBigIntLE()(GHSA-3gc7-fjrx-p6mg)@solana/spl-token>@solana/buffer-layout-utils>bigint-bufferlangsmith@0.3.87 - 4 advisories: SSRF (GHSA-v34v-rq6j-cj6p), prototype pollution (GHSA-fw9q-39r9-c252), streaming redaction bypass (GHSA-rr7j-v2q5-chgv), untrusted manifest deserialization (GHSA-3644-q5cj-c5c7)
@langchain/core@0.3.80>langsmith@0.3.87langsmith@0.7.2(latest) has fixed all 4.@langchain/core@1.1.48also drops the vulnerable uuid dep. Bumping@langchain/corefrom 0.3.x to 1.x would resolve these.MODERATE (7)
jayson@4.3.0(jayson latest still pins uuid@^8) - missing buffer bounds check@langchain/core@0.3.80/langsmith@0.3.87- same vulnContext
We maintain a SAK plugin (piquesignal-solana-agent-plugin) and ran a full audit before our public launch. None of these vulns are reachable from our plugin code, but they show up for every consumer running
npm audit, which creates friction for adoption.Not a demand for immediate action, just flagging for visibility. Happy to help test if patches land.
Environment