# Security Audit Report — @shopsavvy/mcp-server - **Report ID:** `e49a744e-eb9b-4389-b80e-bf2d6e5a160e` - **Generated:** 2026-07-22T05:27:12.556142+00:00 - **Signature:** unsigned (cosign keyless signing runs in CI; Req 22.4) ## 1. Executive Summary **Badge:** Unsafe (composite) **Security score:** 45.67 | Scanner | Badge | | --- | --- | | agent-audit-kit | Caution | | agentshield | Verified | | bearer | Verified | | cisco-skill-scanner | Caution | | nerlo-behavioral | Verified | | nerlo-install-instruction | Verified | | osv-scanner | Unsafe | | trivy | Unsafe | | Severity | Findings | | --- | --- | | critical | 0 | | high | 17 | | medium | 30 | | low | 11 | @shopsavvy/mcp-server is NOT recommended for integration: the scan surfaced 0 critical and 17 high-severity findings. Treat the Per-Scanner Detail section as a remediation worklist and re-scan before reconsidering. ## 2. Source Provenance - **Repository:** https://github.com/shopsavvy/shopsavvy-mcp-server - **Commit scanned:** `unknown` - **License:** MIT - **Maintainer:** ShopSavvy by Monolith Technologies, Inc. - **Version:** 1.0.4 ## 3. Per-Scanner Detail ### agentshield (v1.4.0) — Verified / 100.0 No findings. ### cisco-skill-scanner (v2.0.11) — Caution / 75.0 - **[medium] Moderate analyzability score** — Only 88% of skill content could be analyzed. 1 of 11 files are opaque to the scanner. Some content could not be verified as safe. (/repo:None) - **[low] Vague skill description** — Skill description is too short (16 chars). Provide detailed explanation. (/repo/SKILL.md:None) - **[informational] Skill does not specify a license** — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms. (/repo/SKILL.md:None) - **[medium] Outbound network request primitives in JavaScript/TypeScript** — Pattern detected: fetch( (/repo/src/index.ts:67) - **[medium] Outbound network request primitives in JavaScript/TypeScript** — Pattern detected: fetch( (/repo/src/index.ts:406) - **[medium] Outbound network request primitives in JavaScript/TypeScript** — Pattern detected: fetch( (/repo/src/index.ts:435) - **[low] Vague skill description** — Skill description is too short (16 chars). Provide detailed explanation. (/repo/examples/SKILL.md:None) - **[informational] Skill does not specify a license** — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms. (/repo/examples/SKILL.md:None) ### agent-audit-kit (v0.3.26) — Caution / 73.0 - **[medium] Secret in MCP server environment block** — Hardcoded secret values found in mcpServers env blocks in non-.mcp.json files. (examples/claude-desktop-config.json:9) - **[medium] No lockfile present** — A package manifest exists but no lockfile was found. Without lockfiles, dependency versions float and can be silently updated. (package.json:None) - **[low] MCP server repo missing SECURITY.md or security_contact** — A repository whose name or pyproject keywords declare it as an MCP server ships without a top-level SECURITY.md AND without a 'security_contact' entry in marketplace.json / pyproject.toml / package.json. Anthropic's April 2026 SECURITY.md guidance makes this the baseline expectation so researchers have a channel. (SECURITY.md:None) - **[high] Session token written to log sink in cleartext** — An MCP server, agent, or tool logs a session token, JWT, or Bearer credential through a generic log sink (logger.info / .warn / .error, print) without redaction. CVE-2026-20205 (splunk-mcp-server < 1.0.3) shipped this exact pattern — session tokens ended up in the Splunk '_internal' index, readable by anyone with index-read. Any token written to a log sink is also a supply-chain risk: the log file, shipper, and SIEM are now in scope for the token's blast radius. (src/index.ts:572) ### bearer (v2.0.2) — Verified / 100.0 No findings. ### nerlo-behavioral (v0.1.0) — Verified / 100.0 No findings. ### nerlo-install-instruction (v0.1.0) — Verified / 100.0 No findings. ### trivy (v0.71.0) — Unsafe / 0.0 - **[high] Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default** — MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPServerTransport or SSEServerTransport and has not enabled enableDnsRebindingProtection, a malicious website could exploit DNS rebinding to bypass same-origin policy rest (bun.lock:None) - **[high] Anthropic's MCP TypeScript SDK has a ReDoS vulnerability** — Anthropic's MCP TypeScript SDK versions up to and including 1.25.1 contain a regular expression denial of service (ReDoS) vulnerability in the UriTemplate class when processing RFC 6570 exploded array patterns. The dynamically generated regular expression used during URI matching contains nested quantifiers that can trigger catastrophic backtracking on specially crafted inputs, resulting in excessive CPU consumption. An attacker can exploit this by supplying a malicious URI that causes the Node. (bun.lock:None) - **[high] @modelcontextprotocol/sdk: @modelcontextprotocol/sdk cross-client data leak** — MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.10.0 to 1.25.3, cross-client response data leak when a single McpServer/Server and transport instance is reused across multiple client connections, most commonly in stateless StreamableHTTPServerTransport deployments. This issue has been patched in version 1.26.0. (bun.lock:None) - **[medium] ajv: ReDoS via $data reference** — ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax ($data reference), which is passed directly to the JavaScript RegExp() constructor without validation. An attacker can inject a malicious regex pattern (e.g., "^(a\|a)*$") combined with crafted input to cause catastrophic backtracking. A 31-character payload causes approximately 44 seconds (bun.lock:None) - **[medium] body-parser: body-parser denial of service** — body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic. This issue is addressed in version 2.2.1. (bun.lock:None) - **[low] body-parser: body-parser: Denial of Service via invalid limit option** — Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-pars (bun.lock:None) - **[medium] file-type: file-type: Denial of Service due to infinite loop in ASF file parsing** — file-type detects the file type of a file, stream, or data. Prior to 21.3.1, a denial of service vulnerability exists in the ASF (WMV/WMA) file type detection parser. When parsing a crafted input where an ASF sub-header has a size field of zero, the parser enters an infinite loop. The payload value becomes negative (-24), causing tokenizer.ignore(payload) to move the read position backwards, so the same sub-header is read repeatedly forever. Any application that uses file-type to detect the type (bun.lock:None) - **[medium] file-type: file-type: Denial of Service via excessive memory growth from crafted ZIP files** — file-type detects the file type of a file, stream, or data. From 20.0.0 to 21.3.1, a crafted ZIP file can trigger excessive memory growth during type detection in file-type when using fileTypeFromBuffer(), fileTypeFromBlob(), or fileTypeFromFile(). The ZIP inflate output limit is enforced for stream-based detection, but not for known-size inputs. As a result, a small compressed ZIP can cause file-type to inflate and process a much larger payload while probing ZIP-based formats such as OOXML. Thi (bun.lock:None) - **[high] path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions** — Impact: A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as '{a}{b}{c}:z'. The generated regex grows exponentially with the number of groups, causing denial of service. Patches: Fixed in version 8.4.0. Workarounds: Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns. (bun.lock:None) - **[medium] path-to-regexp: path-to-regexp: Denial of Service via specially crafted paths with multiple wildcards** — Impact: When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path. Unsafe examples: /*foo-*bar-:baz /*a-:b-*c-:d /x/*a-:b/*c/y Safe examples: /*foo-:bar /*foo-:bar-*baz Patches: Upgrade to version 8.4.0. Workarounds: If you are using multiple wildcard parameters, you can check the regex output with a too (bun.lock:None) - **[medium] qs: qs: Denial of Service via improper input validation in array parsing** — Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1. Summary The arrayLimit option in qs did not enforce limits for bracket notation (a[]=1&a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit should apply uniformly across all array notations. Note: The default parameterLimit of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays la (bun.lock:None) - **[medium] \#\#\# Summary 'qs.stringify' throws 'TypeError' when called with 'arr ...** — \#\#\# Summary 'qs.stringify' throws 'TypeError' when called with 'arrayFormat: 'comma'' and 'encodeValuesOnly: true' on an array containing 'null' or 'undefined'. The throw is synchronous and not handled by any of qs's null-related options ('skipNulls', 'strictNullHandling'). \#\#\# Details In the comma + 'encodeValuesOnly' branch, 'lib/stringify.js:145' mapped the array through the raw encoder before joining: '''js obj = utils.maybeMap(obj, encoder); ''' 'utils.encode' ('lib/uti (bun.lock:None) - **[low] qs: qs's arrayLimit bypass in comma parsing allows denial of service** — \#\#\# Summary The 'arrayLimit' option in qs does not enforce limits for comma-separated values when 'comma: true' is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284). \#\#\# Details When the 'comma' option is set to 'true' (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., '? (bun.lock:None) - **[high] undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames** — Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (bun.lock:None) - **[high] undici: undici: Denial of Service via unbounded memory consumption during WebSocket permessage-deflate decompression** — The undici WebSocket client is vulnerable to a denial-of-service attack via unbounded memory consumption during permessage-deflate decompression. When a WebSocket connection negotiates the permessage-deflate extension, the client decompresses incoming compressed frames without enforcing any limit on the decompressed data size. A malicious WebSocket server can send a small compressed frame (a "decompression bomb") that expands to an extremely large size in memory, causing the Node.js process to e (bun.lock:None) - **[high] undici: undici: Denial of Service via crafted WebSocket frame with large length** — ImpactA server can reply with a WebSocket frame using the 64-bit length form and an extremely large length. undici's ByteParser overflows internal math, ends up in an invalid state, and throws a fatal TypeError that terminates the process. Patches Patched in the undici version v7.24.0 and v6.24.0. Users should upgrade to this version or later. (bun.lock:None) - **[high] undici: Undici: Denial of Service via invalid WebSocket permessage-deflate extension parameter** — ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the server_max_window_bits parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A malicious server can respond with an out-of-range server_max_window_bits value (outside zlib's valid range of 8-15). When the server subsequently sends a compressed frame, the client attempts to cre (bun.lock:None) - **[medium] undici: Undici: HTTP Request Smuggling and Denial of Service due to duplicate Content-Length headers** — Undici allows duplicate HTTP Content-Length headers when they are provided in an array with case-variant names (e.g., Content-Length and content-length). This produces malformed HTTP/1.1 requests with multiple conflicting Content-Length values on the wire. Who is impacted: * Applications using undici.request(), undici.Client, or similar low-level APIs with headers passed as flat arrays * Applications that accept user-controlled header names without case-normalization Potential conseque (bun.lock:None) - **[medium] undici: Undici: HTTP header injection and request smuggling vulnerability** — ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { heade (bun.lock:None) - **[medium] undici: Undici: Denial of Service via excessive decompression steps** — Undici is an HTTP/1.1 client for Node.js. Prior to 7.18.0 and 6.23.0, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. This vulnerability is fixed in 7.18.0 and 6.23.0. (bun.lock:None) - **[medium] undici: Undici: Information disclosure due to improper cache-control header parsing** — Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be serve (bun.lock:None) - **[medium] undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding** — Impact: undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 §5.4 does not specify any decoding and browsers do not decode either. Applications that parse a Set-Cookie header and then forward the parsed value into a response header (proxies, middleware, SSR frameworks) become vulnerable to HTTP response header injection: an attacker-controlled upstream can inj (bun.lock:None) - **[low] undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header** — Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict). Affected applications are those that consume Set-Cookie header (bun.lock:None) - **[low] undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery.** — Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-ali (bun.lock:None) ### osv-scanner (v2.3.8) — Unsafe / 0.0 - **[high] GHSA-345p-7cg4-v4c7 — npm @modelcontextprotocol/sdk@1.17.0** — aliases: CVE-2026-25536, GHSA-345p-7cg4-v4c7 \| CVSS: 7.1 (/repo/bun.lock:None) - **[high] GHSA-8r9q-7v3j-jr4g — npm @modelcontextprotocol/sdk@1.17.0** — aliases: CVE-2026-0621, GHSA-8r9q-7v3j-jr4g \| CVSS: 8.7 (/repo/bun.lock:None) - **[high] GHSA-w48q-cv73-mx4w — npm @modelcontextprotocol/sdk@1.17.0** — aliases: CVE-2025-66414, GHSA-w48q-cv73-mx4w \| CVSS: 7.6 (/repo/bun.lock:None) - **[medium] GHSA-2g4f-4pwh-qvx6 — npm ajv@6.12.6** — aliases: CVE-2025-69873, GHSA-2g4f-4pwh-qvx6 \| CVSS: 5.5 (/repo/bun.lock:None) - **[low] GHSA-v422-hmwv-36x6 — npm body-parser@2.2.0** — aliases: CVE-2026-12590, GHSA-v422-hmwv-36x6 \| CVSS: 3.7 (/repo/bun.lock:None) - **[medium] GHSA-wqch-xfxh-vrr4 — npm body-parser@2.2.0** — aliases: CVE-2025-13466, GHSA-wqch-xfxh-vrr4 \| CVSS: 5.5 (/repo/bun.lock:None) - **[medium] GHSA-5v7r-6r5c-r473 — npm file-type@21.0.0** — aliases: CVE-2026-31808, GHSA-5v7r-6r5c-r473 \| CVSS: 5.3 (/repo/bun.lock:None) - **[medium] GHSA-j47w-4g3g-c36v — npm file-type@21.0.0** — aliases: CVE-2026-32630, GHSA-j47w-4g3g-c36v \| CVSS: 5.3 (/repo/bun.lock:None) - **[medium] GHSA-27v5-c462-wpq7 — npm path-to-regexp@8.2.0** — aliases: CVE-2026-4923, GHSA-27v5-c462-wpq7 \| CVSS: 5.9 (/repo/bun.lock:None) - **[high] GHSA-j3q9-mxjg-w52f — npm path-to-regexp@8.2.0** — aliases: CVE-2026-4926, GHSA-j3q9-mxjg-w52f \| CVSS: 7.5 (/repo/bun.lock:None) - **[medium] GHSA-6rw7-vpxm-498p — npm qs@6.14.0** — aliases: CVE-2025-15284, GHSA-6rw7-vpxm-498p \| CVSS: 6.3 (/repo/bun.lock:None) - **[medium] GHSA-q8mj-m7cp-5q26 — npm qs@6.14.0** — aliases: CVE-2026-8723, GHSA-q8mj-m7cp-5q26 \| CVSS: 6.3 (/repo/bun.lock:None) - **[low] GHSA-w7fw-mjwx-w883 — npm qs@6.14.0** — aliases: CVE-2026-2391, GHSA-w7fw-mjwx-w883 \| CVSS: 3.7 (/repo/bun.lock:None) - **[medium] GHSA-2mjp-6q6p-2qxm — npm undici@7.12.0** — aliases: CVE-2026-1525, GHSA-2mjp-6q6p-2qxm \| CVSS: 6.5 (/repo/bun.lock:None) - **[low] GHSA-35p6-xmwp-9g52 — npm undici@7.12.0** — aliases: CVE-2026-6733, GHSA-35p6-xmwp-9g52 \| CVSS: 3.7 (/repo/bun.lock:None) - **[medium] GHSA-4992-7rv2-5pvq — npm undici@7.12.0** — aliases: CVE-2026-1527, GHSA-4992-7rv2-5pvq \| CVSS: 4.6 (/repo/bun.lock:None) - **[high] GHSA-f269-vfmq-vjvj — npm undici@7.12.0** — aliases: CVE-2026-1528, GHSA-f269-vfmq-vjvj \| CVSS: 7.5 (/repo/bun.lock:None) - **[low] GHSA-g8m3-5g58-fq7m — npm undici@7.12.0** — aliases: CVE-2026-11525, GHSA-g8m3-5g58-fq7m \| CVSS: 3.7 (/repo/bun.lock:None) - **[medium] GHSA-g9mf-h72j-4rw9 — npm undici@7.12.0** — aliases: CVE-2026-22036, GHSA-g9mf-h72j-4rw9 \| CVSS: 5.9 (/repo/bun.lock:None) - **[medium] GHSA-p88m-4jfj-68fv — npm undici@7.12.0** — aliases: CVE-2026-9679, GHSA-p88m-4jfj-68fv \| CVSS: 5.9 (/repo/bun.lock:None) - **[medium] GHSA-pr7r-676h-xcf6 — npm undici@7.12.0** — aliases: CVE-2026-9678, GHSA-pr7r-676h-xcf6 \| CVSS: 5.9 (/repo/bun.lock:None) - **[high] GHSA-v9p9-hfj2-hcw8 — npm undici@7.12.0** — aliases: CVE-2026-2229, GHSA-v9p9-hfj2-hcw8 \| CVSS: 7.5 (/repo/bun.lock:None) - **[high] GHSA-vrm6-8vpv-qv8q — npm undici@7.12.0** — aliases: CVE-2026-1526, GHSA-vrm6-8vpv-qv8q \| CVSS: 7.5 (/repo/bun.lock:None) - **[high] GHSA-vxpw-j846-p89q — npm undici@7.12.0** — aliases: CVE-2026-12151, GHSA-vxpw-j846-p89q \| CVSS: 7.5 (/repo/bun.lock:None) ## 4. Threat Model Threat model synthesis has not yet run for this scan. This section is generated by the registry's LLM pipeline (Req 22.3) and will appear in the next regeneration of this report. ## 5. Audit Chain - **Scan job:** `4619ad05-f0fb-49a1-be63-7c9c03364593` - **Completed:** 2026-07-21T03:55:15.991416+00:00 - **Scanner base image:** `us-central1-docker.pkg.dev/nerlo-vsk-prod/nerlo/scanner-base@sha256:65817f4fb3e818a3e792f04b1ce1ebe213e663adb4d71ceae96771bcd197c695` - **AI decision log entries:** 1 - `67b6fbf5-8318-4919-8ca0-978143ed8beb` ## 6. Appendix — Raw Scanner Output ```json [ { "scanner_name": "agentshield", "scanner_version": "1.4.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 7.367328540000017, "status": "complete", "metadata": { "source": "npm", "source_url": "https://www.npmjs.com/package/ecc-agentshield", "install_command": "npm install -g ecc-agentshield@1.4.0", "scans_performed": [ "supply_chain" ] }, "display_score": 100.0, "display_badge": "Verified" }, { "scanner_name": "cisco-skill-scanner", "scanner_version": "2.0.11", "score": 75.0, "scanner_badge": "Caution", "findings": [ { "tool_name": "cisco-skill-scanner", "severity": "medium", "category": "policy_violation", "file_path": "/repo", "line_number": null, "rule_identifier": "LOW_ANALYZABILITY", "title": "Moderate analyzability score", "description": "Only 88% of skill content could be analyzed. 1 of 11 files are opaque to the scanner. Some content could not be verified as safe.", "remediation": "Review opaque files and replace with inspectable formats where possible." }, { "tool_name": "cisco-skill-scanner", "severity": "low", "category": "social_engineering", "file_path": "/repo/SKILL.md", "line_number": null, "rule_identifier": "SOCIAL_ENG_VAGUE_DESCRIPTION", "title": "Vague skill description", "description": "Skill description is too short (16 chars). Provide detailed explanation.", "remediation": "Provide a clear, detailed description of what the skill does and when to use it" }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "policy_violation", "file_path": "/repo/SKILL.md", "line_number": null, "rule_identifier": "MANIFEST_MISSING_LICENSE", "title": "Skill does not specify a license", "description": "Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.", "remediation": "Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)" }, { "tool_name": "cisco-skill-scanner", "severity": "medium", "category": "data_exfiltration", "file_path": "/repo/src/index.ts", "line_number": 67, "rule_identifier": "DATA_EXFIL_JS_NETWORK", "title": "Outbound network request primitives in JavaScript/TypeScript", "description": "Pattern detected: fetch(", "remediation": "Ensure network operations are necessary and document allowed destinations" }, { "tool_name": "cisco-skill-scanner", "severity": "medium", "category": "data_exfiltration", "file_path": "/repo/src/index.ts", "line_number": 406, "rule_identifier": "DATA_EXFIL_JS_NETWORK", "title": "Outbound network request primitives in JavaScript/TypeScript", "description": "Pattern detected: fetch(", "remediation": "Ensure network operations are necessary and document allowed destinations" }, { "tool_name": "cisco-skill-scanner", "severity": "medium", "category": "data_exfiltration", "file_path": "/repo/src/index.ts", "line_number": 435, "rule_identifier": "DATA_EXFIL_JS_NETWORK", "title": "Outbound network request primitives in JavaScript/TypeScript", "description": "Pattern detected: fetch(", "remediation": "Ensure network operations are necessary and document allowed destinations" }, { "tool_name": "cisco-skill-scanner", "severity": "low", "category": "social_engineering", "file_path": "/repo/examples/SKILL.md", "line_number": null, "rule_identifier": "SOCIAL_ENG_VAGUE_DESCRIPTION", "title": "Vague skill description", "description": "Skill description is too short (16 chars). Provide detailed explanation.", "remediation": "Provide a clear, detailed description of what the skill does and when to use it" }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "policy_violation", "file_path": "/repo/examples/SKILL.md", "line_number": null, "rule_identifier": "MANIFEST_MISSING_LICENSE", "title": "Skill does not specify a license", "description": "Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.", "remediation": "Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)" } ], "execution_duration_seconds": 47.63964253300219, "status": "complete", "metadata": { "source": "pypi", "source_url": "https://pypi.org/project/cisco-ai-skill-scanner/2.0.11/", "report_type": "cisco-skill-sast", "analyzers_used": [ "bytecode", "pipeline", "static_analyzer" ], "skills_scanned": [ "repo", "examples" ], "install_command": "pip install --require-hashes -r docker/scanner-base/cisco-skill-scanner/requirements.txt", "severity_counts": { "low": 2, "high": 0, "medium": 4, "critical": 0, "informational": 2 } }, "display_score": 75.0, "display_badge": "Caution" }, { "scanner_name": "agent-audit-kit", "scanner_version": "0.3.26", "score": 73.0, "scanner_badge": "Caution", "findings": [ { "tool_name": "agent-audit-kit", "severity": "medium", "category": "secret-exposure", "file_path": "examples/claude-desktop-config.json", "line_number": 9, "rule_identifier": "AAK-SECRET-007", "title": "Secret in MCP server environment block", "description": "Hardcoded secret values found in mcpServers env blocks in non-.mcp.json files.", "remediation": "Use environment variable references." }, { "tool_name": "agent-audit-kit", "severity": "medium", "category": "supply-chain", "file_path": "package.json", "line_number": null, "rule_identifier": "AAK-SUPPLY-004", "title": "No lockfile present", "description": "A package manifest exists but no lockfile was found. Without lockfiles, dependency versions float and can be silently updated.", "remediation": "Generate and commit lockfile." }, { "tool_name": "agent-audit-kit", "severity": "low", "category": "supply-chain", "file_path": "SECURITY.md", "line_number": null, "rule_identifier": "AAK-SEC-MD-001", "title": "MCP server repo missing SECURITY.md or security_contact", "description": "A repository whose name or pyproject keywords declare it as an MCP server ships without a top-level SECURITY.md AND without a `security_contact` entry in marketplace.json / pyproject.toml / package.json. Anthropic's April 2026 SECURITY.md guidance makes this the baseline expectation so researchers have a channel.", "remediation": "Add SECURITY.md at the repo root with a disclosure email and response SLA; OR add `security_contact` to the project manifest." }, { "tool_name": "agent-audit-kit", "severity": "high", "category": "secret-exposure", "file_path": "src/index.ts", "line_number": 572, "rule_identifier": "AAK-SPLUNK-TOKLOG-001", "title": "Session token written to log sink in cleartext", "description": "An MCP server, agent, or tool logs a session token, JWT, or Bearer credential through a generic log sink (logger.info / .warn / .error, print) without redaction. CVE-2026-20205 (splunk-mcp-server < 1.0.3) shipped this exact pattern \u2014 session tokens ended up in the Splunk `_internal` index, readable by anyone with index-read. Any token written to a log sink is also a supply-chain risk: the log file, shipper, and SIEM are now in scope for the token's blast radius.", "remediation": "Redact token-shaped values before logging. Never interpolate a raw `Authorization`, `Bearer`, JWT, `splunkd_session`, or `st-` credential into a log message. Pin `splunk-mcp-server >= 1.0.3`." } ], "execution_duration_seconds": 10.87141828899621, "status": "complete", "metadata": { "source": "pypi", "source_url": "https://pypi.org/project/agent-audit-kit/0.3.26/", "report_type": "agent-audit-kit-sast", "files_scanned": 9, "install_command": "pip install --require-hashes -r docker/scanner-base/agent-audit-kit/requirements.txt", "rules_evaluated": 211, "severity_counts": { "low": 1, "high": 1, "medium": 2, "critical": 0, "informational": 0 } }, "display_score": 73.0, "display_badge": "Caution" }, { "scanner_name": "bearer", "scanner_version": "2.0.2", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 15.247316896013217, "status": "complete", "metadata": { "source": "github-releases", "source_url": "https://github.com/Bearer/bearer", "report_type": "security", "rules_loaded": 1, "install_command": "curl -sfL https://raw.githubusercontent.com/Bearer/bearer/main/contrib/install.sh | sh -s -- -b /usr/local/bin \"v2.0.2\"" }, "display_score": 100.0, "display_badge": "Verified" }, { "scanner_name": "nerlo-behavioral", "scanner_version": "0.1.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 53.53093205799814, "status": "complete", "metadata": { "source": "nerlo-original", "source_url": "https://github.com/nerlo-ai/nerlo", "report_type": "nerlo-behavioral", "ruleset_path": "/opt/nerlo-rules/exfiltration.yaml", "files_scanned": 1, "install_command": "pip install 'semgrep==1.97.0'" }, "display_score": 100.0, "display_badge": "Verified" }, { "scanner_name": "nerlo-install-instruction", "scanner_version": "0.1.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 52.758217947004596, "status": "complete", "metadata": { "source": "nerlo-original", "source_url": "https://github.com/nerlo-ai/nerlo", "report_type": "nerlo-install-instruction", "ruleset_path": "/opt/nerlo-rules/install_instructions.yaml", "files_scanned": 3, "install_command": "pip install 'semgrep==1.97.0'" }, "display_score": 100.0, "display_badge": "Verified" }, { "scanner_name": "trivy", "scanner_version": "0.71.0", "score": 0.0, "scanner_badge": "Unsafe", "findings": [ { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2025-66414", "title": "Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default", "description": "MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPServerTransport or SSEServerTransport and has not enabled enableDnsRebindingProtection, a malicious website could exploit DNS rebinding to bypass same-origin policy rest", "remediation": "Upgrade @modelcontextprotocol/sdk from 1.17.0 to 1.24.0 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-0621", "title": "Anthropic's MCP TypeScript SDK has a ReDoS vulnerability", "description": "Anthropic's MCP TypeScript SDK versions up to and including 1.25.1 contain a regular expression denial of service (ReDoS) vulnerability in the UriTemplate class when processing RFC 6570 exploded array patterns. The dynamically generated regular expression used during URI matching contains nested quantifiers that can trigger catastrophic backtracking on specially crafted inputs, resulting in excessive CPU consumption. An attacker can exploit this by supplying a malicious URI that causes the Node.", "remediation": "Upgrade @modelcontextprotocol/sdk from 1.17.0 to 1.25.2 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-25536", "title": "@modelcontextprotocol/sdk: @modelcontextprotocol/sdk cross-client data leak", "description": "MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.10.0 to 1.25.3, cross-client response data leak when a single McpServer/Server and transport instance is reused across multiple client connections, most commonly in stateless StreamableHTTPServerTransport deployments. This issue has been patched in version 1.26.0.", "remediation": "Upgrade @modelcontextprotocol/sdk from 1.17.0 to 1.26.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2025-69873", "title": "ajv: ReDoS via $data reference", "description": "ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax ($data reference), which is passed directly to the JavaScript RegExp() constructor without validation. An attacker can inject a malicious regex pattern (e.g., \"^(a|a)*$\") combined with crafted input to cause catastrophic backtracking. A 31-character payload causes approximately 44 seconds", "remediation": "Upgrade ajv from 6.12.6 to 8.18.0, 6.14.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2025-13466", "title": "body-parser: body-parser denial of service", "description": "body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.\nThis issue is addressed in version 2.2.1.", "remediation": "Upgrade body-parser from 2.2.0 to 2.2.1 or later" }, { "tool_name": "trivy", "severity": "low", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-12590", "title": "body-parser: body-parser: Denial of Service via invalid limit option", "description": "Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-pars", "remediation": "Upgrade body-parser from 2.2.0 to 1.20.6, 2.3.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-31808", "title": "file-type: file-type: Denial of Service due to infinite loop in ASF file parsing", "description": "file-type detects the file type of a file, stream, or data. Prior to 21.3.1, a denial of service vulnerability exists in the ASF (WMV/WMA) file type detection parser. When parsing a crafted input where an ASF sub-header has a size field of zero, the parser enters an infinite loop. The payload value becomes negative (-24), causing tokenizer.ignore(payload) to move the read position backwards, so the same sub-header is read repeatedly forever. Any application that uses file-type to detect the type", "remediation": "Upgrade file-type from 21.0.0 to 21.3.1 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-32630", "title": "file-type: file-type: Denial of Service via excessive memory growth from crafted ZIP files", "description": "file-type detects the file type of a file, stream, or data. From 20.0.0 to 21.3.1, a crafted ZIP file can trigger excessive memory growth during type detection in file-type when using fileTypeFromBuffer(), fileTypeFromBlob(), or fileTypeFromFile(). The ZIP inflate output limit is enforced for stream-based detection, but not for known-size inputs. As a result, a small compressed ZIP can cause file-type to inflate and process a much larger payload while probing ZIP-based formats such as OOXML. Thi", "remediation": "Upgrade file-type from 21.0.0 to 21.3.2 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-4926", "title": "path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions", "description": "Impact:\n\nA bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as `{a}{b}{c}:z`. The generated regex grows exponentially with the number of groups, causing denial of service.\n\nPatches:\n\nFixed in version 8.4.0.\n\nWorkarounds:\n\nLimit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.", "remediation": "Upgrade path-to-regexp from 8.2.0 to 8.4.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-4923", "title": "path-to-regexp: path-to-regexp: Denial of Service via specially crafted paths with multiple wildcards", "description": "Impact:\n\nWhen using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.\n\nUnsafe examples:\n\n/*foo-*bar-:baz\n/*a-:b-*c-:d\n/x/*a-:b/*c/y\n\nSafe examples:\n\n/*foo-:bar\n/*foo-:bar-*baz\n\nPatches:\n\nUpgrade to version 8.4.0.\n\nWorkarounds:\n\nIf you are using multiple wildcard parameters, you can check the regex output with a too", "remediation": "Upgrade path-to-regexp from 8.2.0 to 8.4.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2025-15284", "title": "qs: qs: Denial of Service via improper input validation in array parsing", "description": "Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1.\n\n\nSummary\n\nThe arrayLimit\u00a0option in qs did not enforce limits for bracket notation (a[]=1&a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit\u00a0should apply uniformly across all array notations.\n\nNote:\u00a0The default parameterLimit\u00a0of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays la", "remediation": "Upgrade qs from 6.14.0 to 6.14.1 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-8723", "title": "### Summary `qs.stringify` throws `TypeError` when called with `arr ...", "description": "### Summary\n\n\n\n`qs.stringify` throws `TypeError` when called with `arrayFormat: 'comma'` and `encodeValuesOnly: true` on an array containing `null` or `undefined`. The throw is synchronous and not handled by any of qs's null-related options (`skipNulls`, `strictNullHandling`).\n\n\n\n### Details\n\n\n\nIn the comma + `encodeValuesOnly` branch, `lib/stringify.js:145` mapped the array through the raw encoder before joining:\n\n\n\n```js\n\n\n\nobj = utils.maybeMap(obj, encoder);\n\n\n\n```\n\n\n\n`utils.encode` (`lib/uti", "remediation": "Upgrade qs from 6.14.0 to 6.15.2 or later" }, { "tool_name": "trivy", "severity": "low", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-2391", "title": "qs: qs's arrayLimit bypass in comma parsing allows denial of service", "description": "### Summary\nThe `arrayLimit` option in qs does not enforce limits for comma-separated values when `comma: true` is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284).\n\n### Details\nWhen the `comma` option is set to `true` (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., `?", "remediation": "Upgrade qs from 6.14.0 to 6.14.2 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-12151", "title": "undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames", "description": "Impact:\nThe undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service.\n\nAffected applications are those using the undici WebSocket client", "remediation": "Upgrade undici from 7.12.0 to 6.27.0, 7.28.0, 8.5.0 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-1526", "title": "undici: undici: Denial of Service via unbounded memory consumption during WebSocket permessage-deflate decompression", "description": "The undici WebSocket client is vulnerable to a denial-of-service attack via unbounded memory consumption during permessage-deflate decompression. When a WebSocket connection negotiates the permessage-deflate extension, the client decompresses incoming compressed frames without enforcing any limit on the decompressed data size. A malicious WebSocket server can send a small compressed frame (a \"decompression bomb\") that expands to an extremely large size in memory, causing the Node.js process to e", "remediation": "Upgrade undici from 7.12.0 to 6.24.0, 7.24.0 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-1528", "title": "undici: undici: Denial of Service via crafted WebSocket frame with large length", "description": "ImpactA server can reply with a WebSocket frame using the 64-bit length form and an extremely large length. undici's ByteParser overflows internal math, ends up in an invalid state, and throws a fatal TypeError that terminates the process.\n\nPatches\n\nPatched in the undici version v7.24.0 and v6.24.0. Users should upgrade to this version or later.", "remediation": "Upgrade undici from 7.12.0 to 6.24.0, 7.24.0 or later" }, { "tool_name": "trivy", "severity": "high", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-2229", "title": "undici: Undici: Denial of Service via invalid WebSocket permessage-deflate extension parameter", "description": "ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the\u00a0server_max_window_bits\u00a0parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A malicious server can respond with an out-of-range\u00a0server_max_window_bits\u00a0value (outside zlib's valid range of 8-15). When the server subsequently sends a compressed frame, the client attempts to cre", "remediation": "Upgrade undici from 7.12.0 to 6.24.0, 7.24.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-1525", "title": "undici: Undici: HTTP Request Smuggling and Denial of Service due to duplicate Content-Length headers", "description": "Undici allows duplicate HTTP\u00a0Content-Length\u00a0headers when they are provided in an array with case-variant names (e.g.,\u00a0Content-Length\u00a0and\u00a0content-length). This produces malformed HTTP/1.1 requests with multiple conflicting\u00a0Content-Length\u00a0values on the wire.\n\nWho is impacted:\n\n * Applications using\u00a0undici.request(),\u00a0undici.Client, or similar low-level APIs with headers passed as flat arrays\n * Applications that accept user-controlled header names without case-normalization\n\n\nPotential conseque", "remediation": "Upgrade undici from 7.12.0 to 6.24.0, 7.24.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-1527", "title": "undici: Undici: HTTP header injection and request smuggling vulnerability", "description": "ImpactWhen an application passes user-controlled input to the\u00a0upgrade\u00a0option of\u00a0client.request(), an attacker can inject CRLF sequences (\\r\\n) to:\n\n * Inject arbitrary HTTP headers\n * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch)\nThe vulnerability exists because undici writes the\u00a0upgrade\u00a0value directly to the socket without validating for invalid header characters:\n\n// lib/dispatcher/client-h1.js:1121\nif (upgrade) {\n heade", "remediation": "Upgrade undici from 7.12.0 to 6.24.0, 7.24.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-22036", "title": "undici: Undici: Denial of Service via excessive decompression steps", "description": "Undici is an HTTP/1.1 client for Node.js. Prior to 7.18.0 and 6.23.0, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. This vulnerability is fixed in 7.18.0 and 6.23.0.", "remediation": "Upgrade undici from 7.12.0 to 7.18.2, 6.23.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-9678", "title": "undici: Undici: Information disclosure due to improper cache-control header parsing", "description": "Impact:\nUndici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=\" authorization\" or no-cache=\"\\tauthorization\". The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored.\n\nIn shared-cache mode, this allows a response containing one user's authenticated data to be serve", "remediation": "Upgrade undici from 7.12.0 to 7.28.0, 8.5.0 or later" }, { "tool_name": "trivy", "severity": "medium", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-9679", "title": "undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding", "description": "Impact:\nundici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 \u00a75.4 does not specify any decoding and browsers do not decode either.\n\nApplications that parse a Set-Cookie header and then forward the parsed value into a response header (proxies, middleware, SSR frameworks) become vulnerable to HTTP response header injection: an attacker-controlled upstream can inj", "remediation": "Upgrade undici from 7.12.0 to 6.27.0, 7.28.0, 8.5.0 or later" }, { "tool_name": "trivy", "severity": "low", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-11525", "title": "undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header", "description": "Impact:\nWhen undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).\n\nAffected applications are those that consume Set-Cookie header", "remediation": "Upgrade undici from 7.12.0 to 6.27.0, 7.28.0, 8.5.0 or later" }, { "tool_name": "trivy", "severity": "low", "category": "bun", "file_path": "bun.lock", "line_number": null, "rule_identifier": "CVE-2026-6733", "title": "undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery.", "description": "Impact:\nUndici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests.\n\nThis requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-ali", "remediation": "Upgrade undici from 7.12.0 to 6.27.0, 7.28.0, 8.5.0 or later" } ], "execution_duration_seconds": 2.3743029460019898, "status": "complete", "metadata": { "source": "github-releases", "source_url": "https://github.com/aquasecurity/trivy/releases/tag/v0.71.0", "report_type": "filesystem-vulnerability", "install_command": "curl -sfL -o /tmp/trivy.deb https://github.com/aquasecurity/trivy/releases/download/v0.71.0/trivy_0.71.0_Linux-64bit.deb && echo ' /tmp/trivy.deb' | sha256sum -c - && dpkg -i /tmp/trivy.deb", "severity_counts": { "low": 4, "high": 8, "medium": 12, "critical": 0, "informational": 0 }, "manifests_scanned": [ "bun.lock" ] }, "display_score": 0.0, "display_badge": "Unsafe" }, { "scanner_name": "osv-scanner", "scanner_version": "2.3.8", "score": 0.0, "scanner_badge": "Unsafe", "findings": [ { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-345p-7cg4-v4c7", "title": "GHSA-345p-7cg4-v4c7 \u2014 npm @modelcontextprotocol/sdk@1.17.0", "description": "aliases: CVE-2026-25536, GHSA-345p-7cg4-v4c7 | CVSS: 7.1", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-8r9q-7v3j-jr4g", "title": "GHSA-8r9q-7v3j-jr4g \u2014 npm @modelcontextprotocol/sdk@1.17.0", "description": "aliases: CVE-2026-0621, GHSA-8r9q-7v3j-jr4g | CVSS: 8.7", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-w48q-cv73-mx4w", "title": "GHSA-w48q-cv73-mx4w \u2014 npm @modelcontextprotocol/sdk@1.17.0", "description": "aliases: CVE-2025-66414, GHSA-w48q-cv73-mx4w | CVSS: 7.6", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-2g4f-4pwh-qvx6", "title": "GHSA-2g4f-4pwh-qvx6 \u2014 npm ajv@6.12.6", "description": "aliases: CVE-2025-69873, GHSA-2g4f-4pwh-qvx6 | CVSS: 5.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "low", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-v422-hmwv-36x6", "title": "GHSA-v422-hmwv-36x6 \u2014 npm body-parser@2.2.0", "description": "aliases: CVE-2026-12590, GHSA-v422-hmwv-36x6 | CVSS: 3.7", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-wqch-xfxh-vrr4", "title": "GHSA-wqch-xfxh-vrr4 \u2014 npm body-parser@2.2.0", "description": "aliases: CVE-2025-13466, GHSA-wqch-xfxh-vrr4 | CVSS: 5.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-5v7r-6r5c-r473", "title": "GHSA-5v7r-6r5c-r473 \u2014 npm file-type@21.0.0", "description": "aliases: CVE-2026-31808, GHSA-5v7r-6r5c-r473 | CVSS: 5.3", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-j47w-4g3g-c36v", "title": "GHSA-j47w-4g3g-c36v \u2014 npm file-type@21.0.0", "description": "aliases: CVE-2026-32630, GHSA-j47w-4g3g-c36v | CVSS: 5.3", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-27v5-c462-wpq7", "title": "GHSA-27v5-c462-wpq7 \u2014 npm path-to-regexp@8.2.0", "description": "aliases: CVE-2026-4923, GHSA-27v5-c462-wpq7 | CVSS: 5.9", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-j3q9-mxjg-w52f", "title": "GHSA-j3q9-mxjg-w52f \u2014 npm path-to-regexp@8.2.0", "description": "aliases: CVE-2026-4926, GHSA-j3q9-mxjg-w52f | CVSS: 7.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-6rw7-vpxm-498p", "title": "GHSA-6rw7-vpxm-498p \u2014 npm qs@6.14.0", "description": "aliases: CVE-2025-15284, GHSA-6rw7-vpxm-498p | CVSS: 6.3", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-q8mj-m7cp-5q26", "title": "GHSA-q8mj-m7cp-5q26 \u2014 npm qs@6.14.0", "description": "aliases: CVE-2026-8723, GHSA-q8mj-m7cp-5q26 | CVSS: 6.3", "remediation": null }, { "tool_name": "osv-scanner", "severity": "low", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-w7fw-mjwx-w883", "title": "GHSA-w7fw-mjwx-w883 \u2014 npm qs@6.14.0", "description": "aliases: CVE-2026-2391, GHSA-w7fw-mjwx-w883 | CVSS: 3.7", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-2mjp-6q6p-2qxm", "title": "GHSA-2mjp-6q6p-2qxm \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-1525, GHSA-2mjp-6q6p-2qxm | CVSS: 6.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "low", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-35p6-xmwp-9g52", "title": "GHSA-35p6-xmwp-9g52 \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-6733, GHSA-35p6-xmwp-9g52 | CVSS: 3.7", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-4992-7rv2-5pvq", "title": "GHSA-4992-7rv2-5pvq \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-1527, GHSA-4992-7rv2-5pvq | CVSS: 4.6", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-f269-vfmq-vjvj", "title": "GHSA-f269-vfmq-vjvj \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-1528, GHSA-f269-vfmq-vjvj | CVSS: 7.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "low", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-g8m3-5g58-fq7m", "title": "GHSA-g8m3-5g58-fq7m \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-11525, GHSA-g8m3-5g58-fq7m | CVSS: 3.7", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-g9mf-h72j-4rw9", "title": "GHSA-g9mf-h72j-4rw9 \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-22036, GHSA-g9mf-h72j-4rw9 | CVSS: 5.9", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-p88m-4jfj-68fv", "title": "GHSA-p88m-4jfj-68fv \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-9679, GHSA-p88m-4jfj-68fv | CVSS: 5.9", "remediation": null }, { "tool_name": "osv-scanner", "severity": "medium", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-pr7r-676h-xcf6", "title": "GHSA-pr7r-676h-xcf6 \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-9678, GHSA-pr7r-676h-xcf6 | CVSS: 5.9", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-v9p9-hfj2-hcw8", "title": "GHSA-v9p9-hfj2-hcw8 \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-2229, GHSA-v9p9-hfj2-hcw8 | CVSS: 7.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-vrm6-8vpv-qv8q", "title": "GHSA-vrm6-8vpv-qv8q \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-1526, GHSA-vrm6-8vpv-qv8q | CVSS: 7.5", "remediation": null }, { "tool_name": "osv-scanner", "severity": "high", "category": "npm", "file_path": "/repo/bun.lock", "line_number": null, "rule_identifier": "GHSA-vxpw-j846-p89q", "title": "GHSA-vxpw-j846-p89q \u2014 npm undici@7.12.0", "description": "aliases: CVE-2026-12151, GHSA-vxpw-j846-p89q | CVSS: 7.5", "remediation": null } ], "execution_duration_seconds": 29.722747721985797, "status": "complete", "metadata": { "source": "github-releases", "source_url": "https://github.com/google/osv-scanner/releases/tag/v2.3.8", "report_type": "osv-vulnerability", "ecosystems_seen": [ "npm" ], "install_command": "curl -sfL -o /usr/local/bin/osv-scanner https://github.com/google/osv-scanner/releases/download/v2.3.8/osv-scanner_linux_amd64 && echo ' /usr/local/bin/osv-scanner' | sha256sum -c - && chmod +x /usr/local/bin/osv-scanner", "severity_counts": { "low": 4, "high": 8, "medium": 12, "critical": 0, "informational": 0 }, "manifests_scanned": [ "/repo/bun.lock" ], "finding_id_aliases": { "GHSA-27v5-c462-wpq7": [ "CVE-2026-4923" ], "GHSA-2g4f-4pwh-qvx6": [ "CVE-2025-69873" ], "GHSA-2mjp-6q6p-2qxm": [ "CVE-2026-1525" ], "GHSA-345p-7cg4-v4c7": [ "CVE-2026-25536" ], "GHSA-35p6-xmwp-9g52": [ "CVE-2026-6733" ], "GHSA-4992-7rv2-5pvq": [ "CVE-2026-1527" ], "GHSA-5v7r-6r5c-r473": [ "CVE-2026-31808" ], "GHSA-6rw7-vpxm-498p": [ "CVE-2025-15284" ], "GHSA-8r9q-7v3j-jr4g": [ "CVE-2026-0621" ], "GHSA-f269-vfmq-vjvj": [ "CVE-2026-1528" ], "GHSA-g8m3-5g58-fq7m": [ "CVE-2026-11525" ], "GHSA-g9mf-h72j-4rw9": [ "CVE-2026-22036" ], "GHSA-j3q9-mxjg-w52f": [ "CVE-2026-4926" ], "GHSA-j47w-4g3g-c36v": [ "CVE-2026-32630" ], "GHSA-p88m-4jfj-68fv": [ "CVE-2026-9679" ], "GHSA-pr7r-676h-xcf6": [ "CVE-2026-9678" ], "GHSA-q8mj-m7cp-5q26": [ "CVE-2026-8723" ], "GHSA-v422-hmwv-36x6": [ "CVE-2026-12590" ], "GHSA-v9p9-hfj2-hcw8": [ "CVE-2026-2229" ], "GHSA-vrm6-8vpv-qv8q": [ "CVE-2026-1526" ], "GHSA-vxpw-j846-p89q": [ "CVE-2026-12151" ], "GHSA-w48q-cv73-mx4w": [ "CVE-2025-66414" ], "GHSA-w7fw-mjwx-w883": [ "CVE-2026-2391" ], "GHSA-wqch-xfxh-vrr4": [ "CVE-2025-13466" ] }, "cross_scanner_correlation": { "only_osv": [], "only_trivy": [], "intersection_ids": [ "CVE-2025-13466", "CVE-2025-15284", "CVE-2025-66414", "CVE-2025-69873", "CVE-2026-0621", "CVE-2026-11525", "CVE-2026-12151", "CVE-2026-12590", "CVE-2026-1525", "CVE-2026-1526", "CVE-2026-1527", "CVE-2026-1528", "CVE-2026-22036", "CVE-2026-2229", "CVE-2026-2391", "CVE-2026-25536", "CVE-2026-31808", "CVE-2026-32630", "CVE-2026-4923", "CVE-2026-4926", "CVE-2026-6733", "CVE-2026-8723", "CVE-2026-9678", "CVE-2026-9679" ] } }, "display_score": 0.0, "display_badge": "Unsafe" } ] ```