Guide
Known vulnerable library version detected
How StackSiren Deep Scan detects this issue and how to fix it. Severity typically high.
Why it matters
Known vulnerable library version detected is a common finding on vibe-coded and AI-built apps that ship client bundles, shared backends or platform defaults without a security pass.
StackSiren reports this from read-only checks (GET, HEAD or OPTIONS only). It does not exploit the issue.
How to fix it
Upgrade the library to a patched release (check the advisory). Prefer npm/pnpm audit or Dependabot/OSV-Scanner in CI so new CVEs surface before deploy.
How StackSiren Deep Scan checks
Deep Scan runs only on hosts you have verified you own (DNS TXT or /.well-known file) and consented to test. Findings include a short evidence string; secret values are masked.
See the Acceptable Use Policy and Active scanning terms for what Deep Scan is and is not.