Quick answers
- Is CVE-2026-44713 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44713 being exploited in the wild.
- How severe is CVE-2026-44713?
- High severity, with a CVSS score of 8.8, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.8.7.
- Is there a fix for CVE-2026-44713?
- 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-44713 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-44713?
- 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 tmux remote-detection component of pam_usb (src/tmux.c). The software reads the user-controlled $TMUX environment variable and interpolates the socket-path component into a shell command string passed to popen() without proper sanitization. Because the variable is placed inside double-quotes, an attacker can use a double-quote character to terminate the string and inject arbitrary shell syntax. Since the PAM stack executes popen() with root privileges, a local attacker can achieve privilege escalation to root without possessing the required physical USB device. This issue is fixed in version 0.8.7 by implementing strict validation of the socket path and client ID.
Affected products
- mcdope pam_usb < 0.8.7
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-05-27: disclosed: CVE published to NVD