Quick answers
- Is CVE-2026-44710 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44710 being exploited in the wild.
- How severe is CVE-2026-44710?
- Medium severity, with a CVSS score of 4.6, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.8.7.
- Is there a fix for CVE-2026-44710?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44710 attacked?
- It is attacked with physical access, in a software library.
- Am I affected by CVE-2026-44710?
- 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 NULL pointer dereference exists in src/device.c of pam_usb prior to version 0.8.7. The software passes the return values of udisks_drive_get_serial(), udisks_drive_get_vendor(), and udisks_drive_get_model() directly to strcmp() without verifying they are non-NULL. According to GIO/UDisks API documentation, these functions return NULL if a device does not expose those fields. An attacker with physical access can insert a USB device (or mass-storage gadget) lacking these descriptors to trigger a SIGSEGV in the PAM module. This crashes the authentication process, potentially locking out all users of the affected service. The issue is fixed in version 0.8.7 by adding explicit NULL checks.
Affected products
- mcdope pam_usb < 0.8.7
Timeline
- 2026-05-07: advisory: GitHub advisory published by maintainer
- 2026-05-27: disclosed: CVE published to NVD