Quick answers
- Is CVE-2026-48066 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48066 being exploited in the wild.
- How severe is CVE-2026-48066?
- Medium severity, with a CVSS score of 5.7, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.9.1.
- Is there a fix for CVE-2026-48066?
- A patch was published on 2026-05-27: Vulnerability fixed in version 0.9.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48066 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-48066?
- Check whether you run Mcdope Pam Usb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A race condition exists in src/log.c of pam_usb due to the use of a process-wide static pointer (pusb_opts) that stores the address of a stack-local variable during PAM invocation. This violates PAM re-entrancy requirements; when multiple threads invoke the PAM stack concurrently, one thread can clobber the pointer with its own stack address. If the second thread returns, the pointer becomes a dangling reference, leading to undefined behavior or a NULL pointer dereference (CWE-476) when the first thread subsequently attempts to log. This can be exploited locally to cause a Denial of Service (DoS) of the authentication process. The issue is fixed in version 0.9.1 by implementing thread-local storage for the affected pointer.
Affected products
- mcdope pam_usb < 0.9.1
Timeline
- 2026-05-23: advisory: GitHub security advisory published
- 2026-05-27: disclosed: CVE-2026-48066 published to NVD
- 2026-05-27: patched: Vulnerability fixed in version 0.9.1