Quick answers
- Is CVE-2026-64667 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64667 being exploited in the wild.
- How severe is CVE-2026-64667?
- Medium severity, with a CVSS score of 4.4, published 11 November 2026.
- Which products and versions are affected?
- Mcdope Pam Usb 0.9.2 and earlier.
- Is there a fix for CVE-2026-64667?
- Yes: fixed in 0.9.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64667 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-64667?
- 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.
How to fix
- Fixed in: 0.9.3
Technical details
A heap out-of-bounds read exists in pusb_get_tty_from_display_server() where a 4096-byte cmdline buffer is read to capacity and then NUL separators are replaced with spaces, destroying the null terminator. When read(2) returns exactly 4096 bytes, subsequent strstr() calls scan past the allocation boundary. The vulnerability requires DISPLAY to be set during PAM authentication and is triggered by any process with a 4096-byte cmdline, a trivial condition for an unprivileged user to create. Impact is limited to crash or Boolean information disclosure via substring matching.
Affected products
- mcdope pam_usb 0.9.2 and earlier
Timeline
- 2026-05-24: disclosed
- 2026-05-26: patched
- 2026-11-11: advisory