CVE-2025-24032

CRITICALNVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% 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, nvd
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.2Exploit: None knownExposed: 0

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 v3
9.2
EG Score
9.2(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
Severity92% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

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.
generic

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

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

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
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2025/02/msg00021.html
github Patch Available

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 / EcosystemFixed in / PatchReleasedSource
ubuntulibpam-pkcs11 (0.6.8-4ubuntu0.1~esm1) @ xenial2026-06-08ubuntu

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 rangeFixed inDependents
pam-pkcs110.6.11-40.6.11-4+deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pam-pkcs110.6.12-10.6.12-1+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pam-pkcs11—0.6.13-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pam-pkcs11—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 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 187 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Same vendor

1 shown

ubuntu:USN-7363-1

Frequently asked(5)

What is CVE-2025-24032?
CVE-2025-24032 is a critical vulnerability 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 certpolicy is set to none (the default value), then pampkcs11 will only check if the user is capable of logging into the token. An attacker may create a different token with the…
When was CVE-2025-24032 disclosed?
CVE-2025-24032 was first published in the National Vulnerability Database on February 10, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24032 actively exploited?
CVE-2025-24032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.8% of all scored CVEs.
What is the CVSS score of CVE-2025-24032?
CVE-2025-24032 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2025-24032?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24032, 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-24032

Explore →

Is Your Infrastructure Affected by CVE-2025-24032?

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

Start Free Scan →Browse All CVEs