Quick answers
- Is CVE-2026-48983 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48983 being exploited in the wild.
- How severe is CVE-2026-48983?
- Medium severity, with a CVSS score of 5.8, published 18 June 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.9.2.
- Is there a fix for CVE-2026-48983?
- A patch was published on 2026-05-23: Version 0.9.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48983 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-48983?
- 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 Time-of-Check Time-of-Use (TOCTOU) race condition exists in src/pad.c of pam_usb. The software uses a check-then-act pattern, calling lstat() to verify a directory's existence before calling mkdir() to create it. A local attacker can exploit this window to replace the target path with a symbolic link to a directory they control. If successful, the application may write one-time pad (OTP) files into the attacker's directory, allowing the attacker to read future authentication pads (High Confidentiality impact) or prevent successful authentication (Low Availability/Integrity impact). The vulnerability is fixed in version 0.9.2 by replacing the lstat/mkdir sequence with a direct mkdir call that handles EEXIST.
Affected products
- mcdope pam_usb < 0.9.2
Timeline
- 2026-05-23: patched: Version 0.9.2 released
- 2026-05-24: advisory: GitHub Security Advisory published
- 2026-06-18: disclosed: CVE published to NVD