// vulnerability wall

What is being reported in npm packages right now

The most recent reviewed advisories from the GitHub Advisory Database, refreshed every hour. Each one says which package and versions are affected and whether a fix exists. Where the underlying mistake is one people also make in their own code, the SixthWall rule that catches it is linked. RSS feed.

Are any of these in your project?

One command checks every installed package against the same database. It reads your lockfile and sends only package names and versions to osv.dev.

npx @sixthwall/cli deps

60 advisories · 6 critical · 31 high · 23 medium · 0 low

  1. File Viewer: DOM XSS via unsafe hyperlink schemes in the legacy DOC renderer

    • @file-viewer/doc <= 2.3.0 → update to 2.3.1
    • msdoc-viewer <= 0.2.1 → update to 0.2.2

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  2. adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS)

    • adm-zip < 0.6.1 → update to 0.6.1
  3. md-editor-v3: XSS via fenced-code language rendering bypass

    • md-editor-v3 <= 6.5.3 → update to 6.5.4

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  4. Opencast: Stored XSS in Paella player via WebVTT/DFXP caption cue text

    • paella-core < 1.50.6 → update to 1.50.6

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  5. @platejs/core HTML deserialization can trigger browser behavior during parsing

    • @platejs/core < 53.3.11 → update to 53.3.11
    • @platejs/core >= 54.0.0-beta.0, <= 54.0.0-beta.1 → no fix published yet

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  6. Svelte devalue: DoS via malformed input

    • devalue < 5.9.1 → update to 5.9.2
  7. libp2p: PeerStore accepts attacker-signed PeerRecords for a victim peer ID and stores certified attacker addresses

    • @libp2p/peer-store >= 8.0.0, < 12.0.24 → update to 12.0.24

    Same mistake in your own code? AI-WEBHOOK-001 (unverified webhooks)

  8. libp2p: Gossipsub StrictSign accepts attacker-signed messages as a victim RSA peer ID

    • @libp2p/gossipsub >= 15.0.0, < 16.0.5 → update to 16.0.5

    Same mistake in your own code? AI-WEBHOOK-001 (unverified webhooks), AI-CRYPTO-001 (signatures not verified)

  9. ExifReader: DoS via Crafted HEIC/AVIF iloc Box - Memory Exhaustion

    • exifreader <= 4.41.0 → update to 4.41.1
  10. Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site

    • @tinacms/auth <= 1.1.3 → update to 1.1.4
    • next-tinacms-azure <= 15.0.0 → update to 15.0.1

    Same mistake in your own code? AI-IDOR-001 (records looked up by id without an owner check)

  11. Redocly CLI: Path traversal when using `split` command

    • @redocly/cli < 1.34.17 → update to 1.34.17
    • @redocly/cli >= 2.0.0, < 2.33.2 → update to 2.33.2

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  12. oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass

    • @orpc/server <= 1.14.7 → update to 1.14.8
  13. @cyclonedx/cyclonedx-npm: Shell Injection via Unsanitized --workspace Argument on Windows

    • @cyclonedx/cyclonedx-npm < 6.0.0 → update to 6.0.0

    Same mistake in your own code? AI-CMD-001 (shell commands built from variables)

  14. Vendure affected by external-authentication account takeover: external login linked to a pre-existing account by email without verification

    • @vendure/core < 3.7.0 → update to 3.7.0
  15. Vendure: Shop API list queries can return non-public entities when filterOperator is OR

    • @vendure/core >= 1.0.0, < 3.6.5 → update to 3.6.5

    Same mistake in your own code? AI-SECRET-002 (secrets exposed to the browser)

  16. Vendure: Unauthenticated ReDoS via `regex` filter on SQLite backends

    • vendure/core <= 3.6.4 → update to 3.6.5
  17. Vendure has stored XSS in the Admin Dashboard via unsafe HTML-stripping (innerHTML) of entity descriptions

    • @vendure/dashboard < 3.6.5 → update to 3.6.5

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  18. Nuxt OG Image has unauthenticated SSRF via `fonts[].path` URL parameter

    • nuxt-og-image >= 6.0.2, < 6.7.0 → update to 6.7.0

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  19. @nuxtjs/mdc's URL sanitizer misses SVG xlink:href and data:text/html, allowing XSS from untrusted markdown at the default configuration

    • @nuxtjs/mdc < 0.22.1 → update to 0.22.1

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  20. node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion

    • node-opcua-transport >= 2.0.0, < 2.170.0 → update to 2.170.0
    • node-opcua-client >= 2.0.0, < 2.170.0 → update to 2.170.0
    • node-opcua >= 2.0.0, < 2.170.0 → update to 2.170.0
  21. @zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover

    • @zereight/mcp-gitlab < 2.1.27 → update to 2.1.27

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  22. @zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery

    • @zereight/mcp-gitlab >= 0.0.1, < 2.1.27 → update to 2.1.27

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  23. @zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport

    • @zereight/mcp-gitlab < 2.1.30 → update to 2.1.30
  24. highSep 15, 2026GHSA-5648-rgj9-v224

    @zereight/mcp-gitlab has multiple safety-control bypasses: execute_graphql read-only + allow-list bypass, unauthenticated transports, session-exhaustion DoS

    • @zereight/mcp-gitlab < 2.1.30 → update to 2.1.30
  25. yayson: Prototype pollution in Store/LegacyStore deserialization

    • yayson <= 4.2.0 → update to 4.3.0

    Same mistake in your own code? AI-INJECT-001 (objects merged from untrusted input)

  26. @Mockoon/commons-server: Unauthenticated admin API + wildcard CORS allows mock-state hijack and secret theft

    • @mockoon/commons-server < 9.7.0 → update to 9.7.0
    • @mockoon/cli < 9.7.0 → update to 9.7.0

    Same mistake in your own code? AI-NEXT-001 (endpoints that never check who is asking), AI-CONFIG-001 (permissive CORS)

  27. @Mockoon/commons-server: Path traversal in templated `filePath` lets a request escape the served directory (prefix-only base check)

    • @mockoon/commons-server <= 9.6.1 → update to 9.7.0
    • @mockoon/cli <= 9.6.1 → update to 9.7.0

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  28. FrontMCP and mcp-from-openapi have bypass of OpenAPI external $ref SSRF fix

    • mcp-from-openapi >= 2.3.0, < 2.5.0 → update to 2.5.0
    • @frontmcp/adapters >= 1.2.1, < 1.5.0 → update to 1.5.0
    • frontmcp >= 1.2.1, < 1.5.0 → update to 1.5.0

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  29. @jhb.software/payload-alt-text-plugin: Alt Text Endpoint Authorization Bypass via Payload Local API `overrideAccess` Omission

    • @jhb.software/payload-alt-text-plugin < 0.8.0 → update to 0.8.0
  30. @argos-ci/core: CI Branch Name OS Command Injection

    • @argos-ci/core <= 6.2.0 → update to 6.2.1

    Same mistake in your own code? AI-CMD-001 (shell commands built from variables)

  31. OmniRoute ACP Custom-Agent Remote Code Execution (RCE)

    • omniroute <= 3.8.50 → no fix published yet

    Same mistake in your own code? AI-NEXT-001 (endpoints that never check who is asking)

  32. n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

    • n8n >= 2.38.0, < 2.38.1 → update to 2.38.1
    • n8n < 2.37.7 → update to 2.37.7
  33. n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched Content

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  34. n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  35. n8n: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment Endpoints

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7
  36. n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  37. n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  38. n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-CRYPTO-001 (signatures not verified)

  39. n8n: Path Injection in Elasticsearch and ElasticSecurity Nodes via Unencoded Identifiers

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  40. n8n: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-INJECT-001 (objects merged from untrusted input)

  41. n8n: Cross-User Active Workflow ID and Lifecycle Event Disclosure via Missing userId Filter

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  42. n8n: Expression Sandbox Escape via Shared Builtin Tampering and Code-Printer Injection Leads to Code Execution

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  43. n8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7
  44. Angular: SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements

    • @angular/platform-server >= 22.0.0, < 22.1.4 → update to 22.1.4
    • @angular/platform-server >= 21.0.0, < 21.2.22 → update to 21.2.22
    • @angular/platform-server >= 20.0.0, < 20.3.30 → update to 20.3.30
    • @angular/platform-server <= 19.2.25 → no fix published yet

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  45. Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR

    • @angular/platform-server >= 22.0.0, < 22.1.4 → update to 22.1.4
    • @angular/platform-server >= 21.0.0, < 21.2.22 → update to 21.2.22
    • @angular/platform-server >= 20.0.0, < 20.3.30 → update to 20.3.30
    • @angular/platform-server <= 19.2.25 → no fix published yet

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  46. Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`

    • @angular/common >= 22.0.0, < 22.1.1 → update to 22.1.1
    • @angular/common >= 21.0.0, < 21.2.20 → update to 21.2.20
    • @angular/common >= 20.0.0, < 20.3.28 → update to 20.3.28
    • @angular/common <= 19.2.25 → no fix published yet

    Same mistake in your own code? AI-SECRET-002 (secrets exposed to the browser)

  47. Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler

    • @angular/core >= 22.0.0, < 22.1.0 → update to 22.1.0
    • @angular/compiler >= 22.0.0, < 22.1.0 → update to 22.1.0
    • @angular/core >= 21.0.0, < 21.2.20 → update to 21.2.20
    • @angular/compiler >= 21.0.0, < 21.2.20 → update to 21.2.20

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  48. n8n: Domain-Restriction Bypass via Unguarded Model-Search Endpoint in OpenAI Chat Model Node

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7

    Same mistake in your own code? AI-SSRF-001 (server fetching caller-supplied URLs)

  49. n8n: Regular Expression Denial of Service in the Default Blocked-File-Pattern Match via a Git Node Clone Path

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  50. n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7
  51. n8n: Expression Sandbox Escape via Class-Field Sanitizer Rebinding Can Lead to Code Execution

    • n8n < 1.123.76 → update to 1.123.76
    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n >= 2.0.0, < 2.37.7 → update to 2.37.7
  52. highSep 10, 2026GHSA-x7m8-jrm8-hpvx

    @eigenpal/docx-editor-react: CSS injection and print-time XSS via unescaped embedded font-family name

    • @eigenpal/docx-editor-core <= 1.8.2 → update to 1.8.3
    • @eigenpal/docx-editor-react <= 1.8.2 → update to 1.8.3

    Same mistake in your own code? AI-XSS-001 (HTML inserted without sanitising)

  53. @openhop/server: Path Traversal in Flow ID File Operations

    • @openhop/server <= 0.3.5 → update to 0.3.6

    Same mistake in your own code? AI-PATH-001 (file paths built from the request)

  54. functype-mcp-server: MCP `set_functype_version` Package Alias RCE via Unsanitized pnpm install + Dynamic Import

    • functype-mcp-server <= 1.4.3 → update to 1.4.4
  55. @yeger/turbo-graph: Unauthenticated Network-Exposed Task Execution via /api/run

    • @yeger/turbo-graph <= 2.8.8 → update to 2.8.12

    Same mistake in your own code? AI-NEXT-001 (endpoints that never check who is asking)

  56. Nuxt Ollama: Public Runtime Config Exposes Ollama API Key to Browser Clients

    • nuxt-ollama >= 1.2.26, < 1.3.1 → update to 1.3.1
  57. smol-toml: Denial of Service via malformed TOML documents

    • smol-toml <= 1.7.0 → update to 1.7.1
  58. n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

    • n8n >= 2.38.0, < 2.38.2 → update to 2.38.2
    • n8n < 2.37.7 → update to 2.37.7
  59. mediumSep 8, 2026GHSA-wmmp-3585-3rmp

    Nodemailer: IDN/Punycode domain allow-list bypass leads to email delivery to an attacker-controlled domain

    • nodemailer < 9.1.0 → update to 9.1.0
  60. highSep 8, 2026GHSA-2x7j-588g-ccc2

    Nodemailer: Quadratic (O(n²)) time complexity in addressparser allows remote denial of service via a crafted address list

    • nodemailer < 9.1.0 → update to 9.1.0

Source: GitHub Advisory Database, reviewed advisories for the npm ecosystem. SixthWall does not write these advisories; it shows them so you can act on them, and links each to the rule that prevents the same class of bug in code you write.