Quick answers
- Is CVE-2026-44709 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44709 being exploited in the wild.
- How severe is CVE-2026-44709?
- High severity, with a CVSS score of 7.8, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.8.7.
- Is there a fix for CVE-2026-44709?
- 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-44709 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-44709?
- 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 command injection vulnerability exists in the pamusb-pinentry component of pam_usb due to the insecure handling of the PINENTRY_FALLBACK_APP environment variable. The application retrieves this variable and passes it directly to subprocess.run() without validation, allowing a local attacker who can influence the process environment to execute arbitrary binaries with the privileges of the pam_usb toolchain. Additionally, the pamusb-keyring-unlock-gnome component was found to interpolate GNOME Keyring passwords into shell command strings, making them visible in the process list (/proc/<pid>/cmdline). These issues are addressed in version 0.8.7 by implementing strict path validation for the fallback application and passing passwords via stdin.
Affected products
- mcdope pam_usb < 0.8.7
Timeline
- 2026-05-07: advisory: Original GitHub advisory published
- 2026-05-27: disclosed: NVD publication date