Skip to main content

DEP001-vulnerable-deps — Known Vulnerable Dependency

Dimension: Security Default severity: High Languages: All (project-level) CWE: CWE-1395 OWASP: A06:2021 – Vulnerable and Outdated Components Last reviewed: 2026-05-06

What it detects​

Checks dependency lock files at the project root against a small bundled offline database of known-vulnerable package versions.

Supported lock files​

FileEcosystem
Cargo.lockRust / Cargo
package-lock.jsonNode.js / npm (v2 format)
requirements.txtPython / pip (exact == pins)

Offline database​

The bundled database covers a representative set of well-known historical CVEs:

PackageAffected prefixCVE
serde_yaml0.*GHSA-qwqr-xp34-m6mj
lodash4.17.* (< 4.17.21)CVE-2021-23337
requests2.* (< 2.31.0)CVE-2023-32681
tar6.1.* (< 6.1.2)CVE-2021-32803
pyyaml5.*CVE-2020-14343
minimist1.2.* (< 1.2.6)CVE-2021-44906
werkzeug2.1.*CVE-2023-25577
ansi-regex5.0.* (< 5.0.1)CVE-2021-3807
setuptools6* (< 65.5.1)CVE-2022-40897
flask1.*CVE-2023-30861

Important: This is a static snapshot — it is not updated automatically. For up-to-date scanning use cargo-audit, npm audit, or pip-audit alongside zuit.

Configuration​

The rule runs automatically. To opt out:

[rules."DEP001-vulnerable-deps"]
enabled = false

Fix guidance​

Upgrade the identified package to a non-vulnerable version. Check the linked CVE advisory for the minimum safe version.

Implementation​

References​