How severe is CVE-2025-4759?

No CVSS score has been assigned to CVE-2025-4759 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-4759?

CVE-2025-4759 affects the following packages: lockfile-lint-api (npm). Ecosystems affected: npm.

How do I fix CVE-2025-4759?

Update lockfile-lint-api to 5.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-4759 is resolved across your whole dependency graph.

How do I detect CVE-2025-4759 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lockfile-lint-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-4759 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-4759 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-4759 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-4759?

CVE-2025-4759 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-4759?

CVE-2025-4759 is classified as CWE-179 (CWE-179). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-4759 published, and has it been updated?

CVE-2025-4759 was published on May 16, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-4759 — lockfile-lint-api

Fix: lirantal/lockfile-lint@9e5305b

CVE-2025-4759 is a CWE-179 vulnerability in lockfile-lint-api. A fix is available for lockfile-lint-api — see the affected versions and patch details below.

lockfile-lint-api Vulnerable to Incorrect Behavior Order

Also known asGHSA-7cfr-5cjf-32p4

Published

May 16, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-4759.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

6other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

lockfile-lint-apinpm

480Kdownloads / week

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lockfile-lint-api`	all versions	5.9.2`npm install lockfile-lint-api@5.9.2`

Affected Products

1 product · 1 configurations

Application

lockfile-lint-apilirantal

< 5.9.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lockfile-lint-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lockfile-lint-api to 5.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-4759 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-4759 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works