CVE-2025-6547

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation.This issue affects pbkdf2: <=3.1.2.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

June 23, 2025

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

On Node.js < 3, pbkdf2 silently disregards Uint8Array input, returning static keys · Advisory · browserify/pbkdf2 · GitHub

https://github.com/browserify/pbkdf2/security/advisories/GHSA-v62p-rq8g-8h59
github_commit

commit e3102a8cd483 (browserify/pbkdf2)

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

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

Vendor Advisories for CVE-2025-6547(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-pipelines/pipelines-hub-ui-rhel8:17720364712026-03-04redhat
redhatopenshift-pipelines/pipelines-hub-api-rhel9:v1.19.4-17648188802025-12-09redhat
redhatrhtas/rekor-search-ui-rhel9:1.2.1-17554567402025-08-25redhat
redhatopenshift-service-mesh/kiali-ossmc-rhel9:2.4.7-17515493902025-07-09redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
pbkdf2—3.1.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 163 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-6547?
CVE-2025-6547 is a critical vulnerability published on June 23, 2025. Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation.This issue affects pbkdf2: <=3.1.2.
When was CVE-2025-6547 disclosed?
CVE-2025-6547 was first published in the National Vulnerability Database on June 23, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-6547 actively exploited?
CVE-2025-6547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.1% of all scored CVEs.
What is the CVSS score of CVE-2025-6547?
CVE-2025-6547 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-6547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-6547, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-6547?

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

Start Free Scan →Browse All CVEs