CVE-2025-24531

In OpenSC pam_pkcs11 before 0.6.13, pam_sm_authenticate() wrongly returns PAM_IGNORE in many error situations (such as an error triggered by a smartcard before login), allowing authentication bypass.

Published: 2026-01-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-24531 is rated Low Risk (27.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-24531

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-17 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-24531

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.4 5.2 [email protected]

Weakness enumeration for CVE-2025-24531

OS Trackers for CVE-2025-24531

vendor priority summary link
debian unimportant CVE-2025-24531 unimportant priority: Debian including 1 source packages (pam-pkcs11), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-24531
redhat medium — https://access.redhat.com/security/cve/CVE-2025-24531
suse critical CVE-2025-24531 severity critical: SUSE including 9 source package names (pam_pkcs11, pam_pkcs11-0.6.12-2.1, …), 59 product×package rows across 35 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (35 product lines)): Known Not Affected 53, Fixed 6. https://www.suse.com/security/cve/CVE-2025-24531/
ubuntu high CVE-2025-24531 high priority: Ubuntu including 1 source packages (pam-pkcs11), 7 status rows across 7 suites (bionic, focal, jammy, noble, oracular, upstream, xenial): not-affected 4, released 2, needs-triage 1. https://ubuntu.com/security/CVE-2025-24531

Affected software / configurations for CVE-2025-24531

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-24531

cvelogic Threat Intelligence