Cyber Resilience

CVE-2025-24531

Published
16 January 2026
Modified
15 April 2026
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2025-24531 is a medium-severity Return of Wrong Status Code (CWE-393) vulnerability. Its CVSS base score is 6.7 (Medium).

Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-6 (Security and Privacy Function Verification) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-393

Related Threats

CVEs Like This One

CVE-2024-49117Shared CWE-393
CVE-2025-5987Shared CWE-393
CVE-2026-53092Shared CWE-393
CVE-2026-55958Shared CWE-393
CVE-2023-37897Shared CWE-393
CVE-2025-32414Shared CWE-393
CVE-2026-9058Shared CWE-393
CVE-2026-42246Shared CWE-393

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation at post-design stages directly exercises code paths and can identify functions returning incorrect status codes.

SI-6 Security and Privacy Function Verification partial match

Verification of correct security/privacy function operation will surface incorrect status codes that alter expected behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices such as code review, unit testing, and static analysis directly prevent incorrect status codes from being returned.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect functions returning wrong status codes.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch incorrect status codes.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper return-value handling and error indication.

References