How severe is CVE-2025-24531?

CVE-2025-24531 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-24531 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-24531?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-24531 have an EU (EUVD) identifier?

Yes. CVE-2025-24531 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206298.

When was CVE-2025-24531 published?

CVE-2025-24531 was published on 2026-01-16 and last updated on 2026-06-17.

CVE-2025-24531

CVE-2025-24531 is a medium-severity vulnerability with a CVSS 3.x base score of 6.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-393.

Key facts

Severity: Medium (CVSS 3.x base score 6.7)
EPSS exploit prediction: 0% (14th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-206298
Weakness: CWE-393
Published: 2026-01-16
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2025-24531?: CVE-2025-24531 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-24531 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-24531?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-24531 have an EU (EUVD) identifier?: Yes. CVE-2025-24531 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206298.
When was CVE-2025-24531 published?: CVE-2025-24531 was published on 2026-01-16 and last updated on 2026-06-17.

References

Other CWE-393 vulnerabilities

CVE-2026-9058 — Critical (CVSS 9.3): Szafir SDK returns a success status code from the cryptographic digital signature verification process (i.e.…
CVE-2024-49117 — High (CVSS 8.8): Windows Hyper-V Remote Code Execution Vulnerability
CVE-2025-5987 — High (CVSS 8.1): A flaw was found in libssh when using the ChaCha20 cipher with the OpenSSL library. If an attacker manages to exhaust…
CVE-2026-53092 — High (CVSS 7.8): In the Linux kernel, the following vulnerability has been resolved: bpf: Fix linked reg delta tracking when src_reg ==…

Browse all CWE-393 vulnerabilities →