Quick answers
- Is CVE-2026-44712 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44712 being exploited in the wild.
- How severe is CVE-2026-44712?
- High severity, with a CVSS score of 8.2, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.8.7.
- Is there a fix for CVE-2026-44712?
- 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-44712 attacked?
- It is attacked with local access or with physical access, in a software library.
- Am I affected by CVE-2026-44712?
- 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
Two command injection vulnerabilities exist in the Python helper tools of pam_usb. In 'pamusb-conf', the device UUID is read from the XML configuration and interpolated into a shell command via 'subprocess.check_output' with 'shell=True'. In 'pamusb-agent', the 'userName' variable from the configuration is passed directly to 'os.system()'. An attacker with physical access can provide a USB device with a malicious filesystem UUID (e.g., containing shell metacharacters) to trigger execution during device setup, or an attacker with high privileges can modify the XML configuration to achieve a scope change and execute arbitrary commands as root. The issue is fixed in version 0.8.7 by implementing UUID validation and migrating to 'subprocess.run' without shell interpolation.
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