CVE-2025-24032

CRITICALNVD 9.29.2
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.2 under NVD CVSS. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS
Sources: EPSS, NVD CVSS

Also known asEUVD-2025-3602 (ENISA EUVD)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. Prior to version 0.6.13, if cert_policy is set to none (the default value), then pam_pkcs11 will only check if the user is capable of logging into the token. An attacker may create a different token with the user's public data (e.g. the user's certificate) and a PIN known to the attacker. If no signature with the private key is required, then the attacker may now login as user with that created token. The default to *not* check the private key's signature has been changed with commit commi6638576892b59a99389043c90a1e7dd4d783b921, so that all versions starting with pam_pkcs11-0.6.0 should be affected. As a workaround, in pam_pkcs11.conf, set at least cert_policy = signature;.

CVSS
9.2
EG Score
9.2CRITICALmedium 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)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
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.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

February 10, 2025

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_release, github.
Web page

CVE-2025-24032: Mitigate Linux PAM module Vulnerability - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-24032-mitigate-linux-pam-module-vulnerability
Web page

CVE-2025-24032: Detect Vulnerability in Linux PAM module - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-24032-detect-vulnerability-in-linux-pam-module
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4058-1] pam-pkcs11 security update

https://lists.debian.org/debian-lts-announce/2025/02/msg00021.html
GitHub advisoryMentions a patch (unverified)

Authentication bypass with default value for `cert_policy` (`none`) · Advisory · OpenSC/pam_pkcs11 · GitHub

https://github.com/OpenSC/pam_pkcs11/security/advisories/GHSA-8r8p-7mgp-vf56
GitHub release Patch Available

Release 0.6.13

Patch available: OpenSC/pam_pkcs11 pam_pkcs11-0.6.13

https://github.com/OpenSC/pam_pkcs11/releases/tag/pam_pkcs11-0.6.13
GitHub commit Patch Available

commit d9530167966a (OpenSC/pam_pkcs11)

Patch available: OpenSC/pam_pkcs11 pam_pkcs11-0.6.13 (contains commit d9530167966a)

https://github.com/OpenSC/pam_pkcs11/commit/d9530167966a77115db6e885d459382a2e52ee9e
GitHub commit Patch Available

commit b665b287ff95 (OpenSC/pam_pkcs11)

Patch available: OpenSC/pam_pkcs11 pam_pkcs11-0.6.13 (contains commit b665b287ff95)

https://github.com/OpenSC/pam_pkcs11/commit/b665b287ff955bbbd9539252ff9f9e2754c3fb48
GitHub commit Patch Available

commit 470263258d1a (OpenSC/pam_pkcs11)

Patch available: OpenSC/pam_pkcs11 pam_pkcs11-0.6.13 (contains commit 470263258d1a)

https://github.com/OpenSC/pam_pkcs11/commit/470263258d1ac59c5eade439c4d9caba0097e6e6

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibpam-pkcs11 (0.6.8-4ubuntu0.1~esm1) @ xenial2026-11-03ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pam-pkcs110.6.11-4
  • every version up to 0.6.11-4+deb11u1: fixed in 0.6.11-4+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pam-pkcs110.6.12-1
  • every version up to 0.6.12-1+deb12u1: fixed in 0.6.12-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pam-pkcs11—
  • every version up to 0.6.13-1: fixed in 0.6.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pam-pkcs11—
  • every version up to 0.6.13-1: fixed in 0.6.13-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 45× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 290 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 190 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-24032?
CVE-2025-24032 is a critical-severity vulnerability; its CVE record was published on February 10, 2025. PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. Prior to version 0.6.13, if cert_policy is set to none (the default value), then pam_pkcs11 will only check if the user is capable of logging into the token. An attacker may create a different token with the…
When was the CVE record for CVE-2025-24032 published?
The CVE record for CVE-2025-24032 was published on February 10, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-24032 actively exploited?
CVE-2025-24032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-24032?
CVE-2025-24032 has a CVSS base score of 9.2 (NVD).
How do I remediate CVE-2025-24032?
A fix for CVE-2025-24032 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-24032?

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