CVE-2025-6545

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2025-18922 (ENISA EUVD) · GHSA-h7cp-r72f-jxh6 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js.

This issue affects pbkdf2: from 3.0.10 through 3.1.2.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 23, 2025

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

pbkdf2 silently returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algorithm strings (even if supported by Node.js) · Advisory · browserify/pbkdf2 · GitHub

https://github.com/browserify/pbkdf2/security/advisories/GHSA-h7cp-r72f-jxh6
GitHub commit

commit e3102a8cd483 (browserify/pbkdf2)

Fix landed in browserify/pbkdf2 commit e3102a8cd483 — awaiting tagged release

https://github.com/browserify/pbkdf2/commit/e3102a8cd4830a3ac85cd0dd011cc002fdde33bb
GitHub commit

commit 9699045c37a0 (browserify/pbkdf2)

Fix landed in browserify/pbkdf2 commit 9699045c37a0 — awaiting tagged release

https://github.com/browserify/pbkdf2/commit/9699045c37a07f8319cfb8d44e2ff4252d7a7078

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunode-pbkdf2 (3.0.16-1ubuntu0.1~esm1) @ focal2026-11-01ubuntu
redhatopenshift-pipelines/pipelines-hub-ui-rhel8:17720364712026-03-04redhat
redhatopenshift-pipelines/pipelines-hub-db-migration-rhel9:v1.19.4-17648190052025-12-09redhat
redhatrhtas/rekor-search-ui-rhel9:1.2.1-17554567402025-08-25redhat
redhatrhdh/rhdh-hub-rhel9:1.7.0-17549364702025-08-19redhat
redhatopenshift-service-mesh/kiali-ossmc-rhel9:2.4.7-17515493902025-07-09redhat
npmpbkdf2 @ 3.1.3 (fixes >= 3.0.10, <= 3.1.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-pbkdf23.1.1-1 ... 3.1.5+~3.1.2-1 (7 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-pbkdf23.1.2-3, 3.1.3+~3.1.2-1, 3.1.5+~3.1.2-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-pbkdf23.1.2-3, 3.1.3+~3.1.2-1, 3.1.5+~3.1.2-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-pbkdf23.1.2-3
  • every version up to 3.1.3+~3.1.2-1: fixed in 3.1.3+~3.1.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
pbkdf2—
  • 3.0.10 up to 3.1.3: fixed in 3.1.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 23× in last 7d / 78× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 261 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-01 12:39 UTCVendor advisory
  3. 2026-11-01 12:39 UTCGHSA enrichmentGHSA-h7cp-r72f-jxh6 · GitHub severity CRITICAL
  4. 2026-11-01 08:02 UTCGHSA enrichmentGHSA-h7cp-r72f-jxh6 · GitHub severity CRITICAL
  5. 2026-11-01 08:02 UTCEG score recompute
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  7. 2026-10-31 12:39 UTCEG score recompute
  8. 2026-10-31 12:39 UTCVendor advisory
  9. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-10-30 12:38 UTCEG score recompute
  11. 2026-10-30 12:38 UTCVendor advisory
  12. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  13. 2026-10-29 12:37 UTCEG score recompute
  14. 2026-10-29 12:37 UTCVendor advisory
  15. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  16. 2026-10-28 12:36 UTCEG score recompute
  17. 2026-10-28 12:36 UTCVendor advisory
  18. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  19. 2026-10-27 12:36 UTCEG score recompute
  20. 2026-10-27 12:36 UTCVendor advisory
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  22. 2026-10-26 12:36 UTCEG score recompute
  23. 2026-10-26 12:36 UTCVendor advisory
  24. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  25. 2026-10-25 16:10 UTCEG score recompute
Show 74 more
  1. 2026-10-25 12:31 UTCEG score recompute
  2. 2026-10-25 12:31 UTCVendor advisory
  3. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-24 12:29 UTCEG score recompute
  5. 2026-10-24 12:29 UTCVendor advisory
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-23 12:27 UTCEG score recompute
  8. 2026-10-23 12:27 UTCVendor advisory
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-22 12:25 UTCEG score recompute
  11. 2026-10-22 12:25 UTCVendor advisory
  12. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-21 12:25 UTCEG score recompute
  14. 2026-10-21 12:25 UTCVendor advisory
  15. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-20 12:25 UTCEG score recompute
  17. 2026-10-20 12:25 UTCVendor advisory
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-19 12:22 UTCEG score recompute
  20. 2026-10-19 12:22 UTCVendor advisory
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-18 10:36 UTCVendor advisory
  23. 2026-10-18 05:19 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-17 08:16 UTCEG score recompute
  26. 2026-10-17 08:16 UTCVendor advisory
  27. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  28. 2026-10-16 08:15 UTCEG score recompute
  29. 2026-10-16 08:15 UTCVendor advisory
  30. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  31. 2026-10-15 07:18 UTCEG score recompute
  32. 2026-10-15 07:18 UTCVendor advisory
  33. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  34. 2026-10-14 03:16 UTCEG score recompute
  35. 2026-10-14 03:16 UTCVendor advisory
  36. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  37. 2026-10-12 23:16 UTCVendor advisory
  38. 2026-10-12 16:49 UTCEG score recompute
  39. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  40. 2026-10-12 10:19 UTCVendor advisory
  41. 2026-10-11 20:23 UTCEG score recompute
  42. 2026-10-11 18:35 UTCEG score recompute
  43. 2026-10-11 15:10 UTCEG score recompute
  44. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  45. 2026-10-10 20:23 UTCOSV refresh
  46. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  47. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  49. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  51. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  53. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  55. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  56. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  57. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  58. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  59. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  60. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-09-21 07:49 UTCOSV refresh
  62. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  63. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  65. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  67. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  68. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  69. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  72. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  73. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  74. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile

Frequently asked(5)

What is CVE-2025-6545?
CVE-2025-6545 is a critical-severity vulnerability; its CVE record was published on June 23, 2025. Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js. This issue affects pbkdf2: from 3.0.10 through 3.1.2.
When was the CVE record for CVE-2025-6545 published?
The CVE record for CVE-2025-6545 was published on June 23, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-6545 actively exploited?
CVE-2025-6545 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-6545?
CVE-2025-6545 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-6545?
A fix for CVE-2025-6545 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-6545 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-6545

Explore →

Is Your Infrastructure Affected by CVE-2025-6545?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.