{"version": "2.1.0", "$schema": "https://json.schemastore.org/sarif-2.1.0.json", "runs": [{"tool": {"driver": {"name": "Repobility", "informationUri": "https://repobility.com", "rules": [{"id": "scanner-39762d64c6242d65", "name": "CVE-2026-59869: js-yaml 4.1.1 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-59869: js-yaml 4.1.1 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "js-yaml: js-yaml: Denial of Service via crafted YAML documents\n\njs-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in versions 3.15.0 and 4.3.0.\n\nPackage: js-yaml\nInstalled: 4.1.1\nFixed in: 3.15.0, 4.3.0\nSeverity: HIGH\nFix: Upgrade js-yaml to 3.15.0, 4.3.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 1.0}}, {"id": "scanner-23f76c83140b1dbe", "name": "CVE-2026-53550: js-yaml 4.1.1 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-53550: js-yaml 4.1.1 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "js-yaml: js-yaml: Denial of Service via crafted YAML merge keys\n\njs-yaml is a JavaScript YAML parser and dumper. Prior to 4.2.0 and 3.15.0, a crafted YAML document can trigger algorithmic CPU exhaustion in js-yaml merge-key processing (<<) by repeating the same alias many times in a merge sequence. This causes quadratic parse-time behavior relative to input size and can block a Node.js worker/event loop for seconds with a relatively small payload (tens of KB), resulting in denial of service. The issue is in merge handling inside lib/loader.js. This vulnerabil\n\nPackage: js-yaml\nInstalled: 4.1.1\nFixed in: 4.2.0, 3.15.0\nSeverity: MEDIUM\nFix: Upgrade js-yaml to 4.2.0, 3.15.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-196bbbe2adca024f", "name": "CVE-2026-12151: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-12151: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames\n\nImpact:\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\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 6.27.0, 7.28.0, 8.5.0\nSeverity: HIGH\nFix: Upgrade undici to 6.27.0, 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 1.0}}, {"id": "scanner-0388c62b37ba042f", "name": "CVE-2026-6734: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-6734: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing\n\nImpact:\nWhen using Socks5ProxyAgent, undici reuses a single connection pool across different origins without verifying that the pool's origin matches the requested origin. All requests are dispatched through the pool connected to the first origin, regardless of the intended destination.\n\nThis causes cross-origin request routing: credentials and request data intended for origin B are sent to origin A, responses from the wrong origin are trusted, and HTTPS requests may be silently downgraded to HT\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 7.28.0, 8.2.0\nSeverity: HIGH\nFix: Upgrade undici to 7.28.0, 8.2.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 1.0}}, {"id": "scanner-7449f2771e6eba20", "name": "CVE-2026-9697: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-9697: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy\n\nImpact:\nundici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert, key, rejectUnauthorized, and servername settings.\n\nApplications that pin to an internal or corporate CA via requestTls.ca will, when their proxy URI is SOCKS5, get the default Mozilla CA bundle as the trust anchor instead. Any cert signed \n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 7.28.0, 8.5.0\nSeverity: HIGH\nFix: Upgrade undici to 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 1.0}}, {"id": "scanner-436f356f378003d0", "name": "CVE-2026-9678: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-9678: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: Undici: Information disclosure due to improper cache-control header parsing\n\nImpact:\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\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 7.28.0, 8.5.0\nSeverity: MEDIUM\nFix: Upgrade undici to 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-56fcb910cd2eea98", "name": "CVE-2026-9679: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-9679: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding\n\nImpact:\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\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 6.27.0, 7.28.0, 8.5.0\nSeverity: MEDIUM\nFix: Upgrade undici to 6.27.0, 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-5625bb717e0b591b", "name": "CVE-2026-11525: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-11525: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header\n\nImpact:\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\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 6.27.0, 7.28.0, 8.5.0\nSeverity: LOW\nFix: Upgrade undici to 6.27.0, 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "low", "confidence": 1.0}}, {"id": "scanner-11780943f11cf5ed", "name": "CVE-2026-6733: undici 7.26.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-6733: undici 7.26.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery.\n\nImpact:\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\n\nPackage: undici\nInstalled: 7.26.0\nFixed in: 6.27.0, 7.28.0, 8.5.0\nSeverity: LOW\nFix: Upgrade undici to 6.27.0, 7.28.0, 8.5.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "low", "confidence": 1.0}}, {"id": "scanner-90ebb6126bfc7765", "name": "CVE-2026-48779: ws 8.20.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-48779: ws 8.20.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "ws: ws: Denial of Service via memory exhaustion from small WebSocket fragments\n\nws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-si\n\nPackage: ws\nInstalled: 8.20.0\nFixed in: 5.2.5, 6.2.4, 7.5.11, 8.21.0\nSeverity: HIGH\nFix: Upgrade ws to 5.2.5, 6.2.4, 7.5.11, 8.21.0"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 1.0}}, {"id": "scanner-5a491364b191b329", "name": "CVE-2026-45736: ws 8.20.0 \u2014 pnpm-lock.yaml", "shortDescription": {"text": "CVE-2026-45736: ws 8.20.0 \u2014 pnpm-lock.yaml"}, "fullDescription": {"text": "ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray`\n\nws is an open source WebSocket client and server for Node.js. Prior to 8.20.1, the websocket.close() implementation is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument. This vulnerability is fixed in 8.20.1.\n\nPackage: ws\nInstalled: 8.20.0\nFixed in: 8.20.1\nSeverity: MEDIUM\nFix: Upgrade ws to 8.20.1"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-e725d2ab884fbd49", "name": "Multiple root agent instruction files without precedence", "shortDescription": {"text": "Multiple root agent instruction files without precedence"}, "fullDescription": {"text": "The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies."}, "properties": {"scanner": "scanner-primary", "layer": "quality", "severity": "low", "confidence": 1.0}}, {"id": "scanner-f3321f3de07fb846", "name": "SkillSpector EA3 (excessive-agency) in LICENSE", "shortDescription": {"text": "SkillSpector EA3 (excessive-agency) in LICENSE"}, "fullDescription": {"text": "NOT LIMITED TO\n\nSkill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.\n\nSkill: unknown\nRule: EA3 Category: excessive-agency\nSeverity: LOW Confidence: 0.70\n\nRemediation: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "low", "confidence": 0.7}}, {"id": "scanner-54028639b4af6313", "name": "SkillSpector PE3 (priv-esc) in electron.vite.config.ts", "shortDescription": {"text": "SkillSpector PE3 (priv-esc) in electron.vite.config.ts"}, "fullDescription": {"text": ".env\n\nCode accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.\n\nSkill: unknown\nRule: PE3 Category: priv-esc\nSeverity: HIGH Confidence: 0.60\n\nRemediation: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 0.6}}, {"id": "scanner-0e68d37fc6045dd4", "name": "SkillSpector RA2 (rogue-agent) in pnpm-lock.yaml", "shortDescription": {"text": "SkillSpector RA2 (rogue-agent) in pnpm-lock.yaml"}, "fullDescription": {"text": "plist\n\nSkill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.\n\nSkill: unknown\nRule: RA2 Category: rogue-agent\nSeverity: MEDIUM Confidence: 0.75\n\nRemediation: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 0.75}}, {"id": "scanner-1474af525032cfbf", "name": "SkillSpector SC1 (supply-chain) in package.json", "shortDescription": {"text": "SkillSpector SC1 (supply-chain) in package.json"}, "fullDescription": {"text": "\"@electron-toolkit/preload\": \"^3.0.2\"\n\nDependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.\n\nSkill: unknown\nRule: SC1 Category: supply-chain\nSeverity: LOW Confidence: 0.40\n\nRemediation: Pin all dependency versions in requirements.txt or pyproject.toml. Use exact versions (==) or compatible ranges. Run pip-audit regularly."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "low", "confidence": 0.4}}, {"id": "scanner-3b5b4d5fd228b862", "name": "SkillSpector SC4 (supply-chain) in package.json", "shortDescription": {"text": "SkillSpector SC4 (supply-chain) in package.json"}, "fullDescription": {"text": "ws==8.20.0\n\nDependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.\n\nSkill: unknown\nRule: SC4 Category: supply-chain\nSeverity: HIGH Confidence: 0.80\n\nRemediation: Update the dependency to a patched version that addresses the known CVE. Check OSV (osv.dev) or NVD for details on the vulnerability."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 0.8}}, {"id": "scanner-c48d54072d7b9202", "name": "SkillSpector SC6 (supply-chain) in package.json", "shortDescription": {"text": "SkillSpector SC6 (supply-chain) in package.json"}, "fullDescription": {"text": "oxlint\n\nPackage name closely resembles a popular package, suggesting possible typosquatting. Attackers publish malicious packages with similar names to trick developers into installing them.\n\nSkill: unknown\nRule: SC6 Category: supply-chain\nSeverity: HIGH Confidence: 0.70\n\nRemediation: Verify the package name is correct and not a typosquatting variant. Compare against the official package name on PyPI or npm."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 0.7}}, {"id": "scanner-32586301a07ba95a", "name": "SkillSpector TM1 (tool-misuse) in pnpm-lock.yaml", "shortDescription": {"text": "SkillSpector TM1 (tool-misuse) in pnpm-lock.yaml"}, "fullDescription": {"text": "rm0YWsqUSRrjncSXGA7Zv78Nbnw4XL6/\n\nTool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).\n\nSkill: unknown\nRule: TM1 Category: tool-misuse\nSeverity: HIGH Confidence: 0.85\n\nRemediation: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "high", "confidence": 0.85}}, {"id": "scanner-e637c415447867e4", "name": "Run SkillSpector's LLM-backed analysis in your own pipeline", "shortDescription": {"text": "Run SkillSpector's LLM-backed analysis in your own pipeline"}, "fullDescription": {"text": "Repobility ran SkillSpector's static rules server-side. The deeper LLM-backed analyzers \u2014 tool-poisoning (TP*), semantic security discovery (SSD*), developer-intent mismatch (SDI*) \u2014 are meant to run on YOUR machine with YOUR model; repobility never sends your code to an LLM. Recipe:\n\n# 1. Install SkillSpector in your own isolated env\npipx install \"skillspector @ git+https://github.com/NVIDIA/SkillSpector.git\"\n\n# 2. Point it at YOUR LLM pipeline (pick one) - your code stays on your machine\nexport SKILLSPECTOR_PROVIDER=anthropic && export ANTHROPIC_API_KEY=sk-ant-...\n# export SKILLSPECTOR_PROVIDER=openai && export OPENAI_API_KEY=sk-...\n# export SKILLSPECTOR_PROVIDER=openai OPENAI_API_KEY=ollama OPENAI_BASE_URL=http://localhost:11434/v1 SKILLSPECTOR_MODEL=llama3.1:8b\n# export SKILLSPECTOR_PROVIDER=nv_build && export NVIDIA_INFERENCE_KEY=nvapi-...\n\n# 3. Run the LLM-backed scan per skill (omit --no-llm to enable the LLM analyzers)\nskillspector scan . --format sarif --output skillspector-"}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "info", "confidence": 1.0}}, {"id": "scanner-9710c8d059e53154", "name": "No frontend routes/components detected", "shortDescription": {"text": "No frontend routes/components detected"}, "fullDescription": {"text": "No React/Vue/Next routes were found. This is fine for backend-only repos."}, "properties": {"scanner": "scanner-primary", "layer": "frontend", "severity": "info", "confidence": 1.0}}, {"id": "scanner-6372cebde0220094", "name": "No auth library detected", "shortDescription": {"text": "No auth library detected"}, "fullDescription": {"text": "The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing."}, "properties": {"scanner": "scanner-primary", "layer": "security", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-cb639d9a10a47b23", "name": "package.json defines install-time lifecycle scripts", "shortDescription": {"text": "package.json defines install-time lifecycle scripts"}, "fullDescription": {"text": "preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access."}, "properties": {"scanner": "scanner-primary", "layer": "cicd", "severity": "low", "confidence": 1.0}}, {"id": "scanner-4601e3ad3bb28677", "name": "No CI/CD pipelines detected", "shortDescription": {"text": "No CI/CD pipelines detected"}, "fullDescription": {"text": "No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints."}, "properties": {"scanner": "scanner-primary", "layer": "cicd", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-749d4bc1bd66df5f", "name": "Agent instructions exist but release-hardening basics are missing", "shortDescription": {"text": "Agent instructions exist but release-hardening basics are missing"}, "fullDescription": {"text": "AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable."}, "properties": {"scanner": "scanner-primary", "layer": "quality", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-9b0b5edfab6b8684", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-39q2-94rc-95cp", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-39q2-94rc-95cp"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-39q2-94rc-95cp (aka CVE-2026-65903).\n\nDOMPurify's ADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluation\n\nAliases: CVE-2026-65903\nAdvisory: https://osv.dev/vulnerability/GHSA-39q2-94rc-95cp\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-6dce387d9d11bf72", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-76mc-f452-cxcm", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-76mc-f452-cxcm"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-76mc-f452-cxcm (aka CVE-2026-65902).\n\nDOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`\n\nAliases: CVE-2026-65902\nAdvisory: https://osv.dev/vulnerability/GHSA-76mc-f452-cxcm\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-526dceb464bb69a9", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-c2j3-45gr-mqc4", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-c2j3-45gr-mqc4"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-c2j3-45gr-mqc4.\n\nDOMPurify: `CUSTOM_ELEMENT_HANDLING` bypasses `afterSanitizeElements` for allowed custom elements.\n\nAdvisory: https://osv.dev/vulnerability/GHSA-c2j3-45gr-mqc4\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "low", "confidence": 1.0}}, {"id": "scanner-ea842b120eb3b0f3", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-cj63-jhhr-wcxv", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-cj63-jhhr-wcxv"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-cj63-jhhr-wcxv (aka CVE-2026-65913).\n\nDOMPurify USE_PROFILES prototype pollution allows event handlers\n\nAliases: CVE-2026-65913\nAdvisory: https://osv.dev/vulnerability/GHSA-cj63-jhhr-wcxv\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-fda66c1879246867", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-cjmm-f4jc-qw8r", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-cjmm-f4jc-qw8r"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-cjmm-f4jc-qw8r (aka CVE-2026-65912).\n\nDOMPurify ADD_ATTR predicate skips URI validation\n\nAliases: CVE-2026-65912\nAdvisory: https://osv.dev/vulnerability/GHSA-cjmm-f4jc-qw8r\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-2d5ee8c79d104dfe", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-cmwh-pvxp-8882", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-cmwh-pvxp-8882"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-cmwh-pvxp-8882 (aka CVE-2026-65898).\n\nDOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)\n\nAliases: CVE-2026-65898\nAdvisory: https://osv.dev/vulnerability/GHSA-cmwh-pvxp-8882\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-9e8b78f5194237e0", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-crv5-9vww-q3g8", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-crv5-9vww-q3g8"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-crv5-9vww-q3g8 (aka CVE-2026-41239).\n\nDOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode\n\nAliases: CVE-2026-41239\nAdvisory: https://osv.dev/vulnerability/GHSA-crv5-9vww-q3g8\nFix: upgrade `dompurify` past the affected range per the advisory."}, "properties": {"scanner": "scanner-primary", "layer": "dependencies", "severity": "medium", "confidence": 1.0}}, {"id": "scanner-9834bbf36de2d99b", "name": "Vulnerable dependency dompurify 3.2.7: GHSA-gvmj-g25r-r7wr", "shortDescription": {"text": "Vulnerable dependency dompurify 3.2.7: GHSA-gvmj-g25r-r7wr"}, "fullDescription": {"text": "OSV.dev reports `dompurify` at version `3.2.7` (resolved in `pnpm-lock.yaml`) is affected by GHSA-gvmj-g25r-r7wr (aka CVE-2026-65900).\n\nDOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside