CVE security advisories and vulnerability history for npm-lockfile by ljharb.
Last updated
ljharb npm-lockfile has 1 published CVE records since 2022, of which 0 are in CISA's Known Exploited Vulnerabilities catalog and 0 have a known public exploit. The average CVSS base score across scored CVEs is 9.8.
This page aggregates every publicly disclosed vulnerability (CVE) affecting ljharb npm-lockfile, with a severity breakdown, the affected and patched versions, the most common weakness types, and the full CVE list.
How the CVSS severity of ljharb npm-lockfile's CVEs breaks down, plus how many are exploited in the wild or have public exploit code.
In CISA’s Known Exploited Vulnerabilities catalog
0
None of ljharb npm-lockfile's CVEs are currently listed in CISA's KEV catalog.
Public exploits
0
No ljharb npm-lockfile CVEs currently have a tracked public exploit.
Browse every ljharb npm-lockfile version named in a CVE, then pick one to see only the CVEs that affect it.
1 CVE
The CWE weakness categories most often found in ljharb npm-lockfile CVEs. Follow any weakness for its full explanation.
Browse vulnerabilities for other products by ljharb.
Common questions about ljharb npm-lockfile vulnerabilities.
Vulnerability data is sourced from the CVE Program; severity, KEV, and exploit signals are aggregated by RadicalNotion.AI.
Monitor new ljharb npm-lockfile vulnerabilities as they are disclosed, with AI-written analysis and remediation guidance.
