CVE-2025-4759: Lirantal lockfile-lint-api vulnerability
Lirantal · lockfile-lint-api
Fixed in 5.9.2 · Affected: Lirantal lockfile-lint-api before 5.9.2 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 38% of scored CVEs
DescriptionCVE.org
Versions of the package lockfile-lint-api before 5.9.2 are vulnerable to Incorrect Behavior Order: Early Validation via the resolved attribute of the package URL validation which can be bypassed by extending the package name allowing an attacker to install other npm packages than the intended one.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- lockfile-lint-apibefore 5.9.2
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2025-4759 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-179cwe.mitre.org
- security.snyk.io/vuln/SNYK-JS-LOCKFILELINTAPI-10169587security.snyk.io
- gist.github.com/Xavier59/881aef04940970dc3e738dcbff64151fgist.github.com
- github.com/lirantal/lockfile-lint/blob/89b5cad028df4d77bab2b73acgithub.com
- github.com/lirantal/lockfile-lint/pull/204github.com
- github.com/lirantal/lockfile-lint/commit/9e5305bd3e4f0c6acc0d23egithub.com