Read the docs

pam_usb deny_remote bypassed by compressed IPv6 addresses

Priority LOW 35CWE-285Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-285.

Summary

pam_usb versions from 0.8.0 before 0.9.3 use /usr/bin/w -i to detect whether the authenticating user has an active remote tmux session when deny_remote is set. The IPv6 regex in pusb_tmux_has_remote_clients() (src/tmux.c) matched only four explicit colon-separated groups, so compressed addresses such as ::1, fe80::1 and 2001:db8::1 did not match. The check then reported no remote clients even when a remote tmux client was connected from such an address, letting a remote attacker bypass deny_remote. The weaknesses are CWE-285 and CWE-693, with a CVSS 3.1 base score of 7.4 (HIGH).

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

pam_usb provides hardware authentication for Linux using removable media. From version 0.8.0 to before version 0.9.3, the deny_remote feature in pam_usb uses /usr/bin/w -i to detect whether the authenticating user has an active remote tmux session. In pusb_tmux_has_remote_clients() (src/tmux.c), the IPv6 detection regex required exactly four explicit colon-separated groups of 1-4 hex digits (e.g. 2001:0db8:85a3:0000). Any IPv6 address in compressed notation — including loopback (::1), link-local (fe80::1), and global unicast addresses (2001:db8::1) — did not match this pattern. As a result the remote-client check silently returned "no remote clients" even when a remote tmux client was connected from such an address. This issue has been patched in version 0.9.3.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00384 33rd percentileScored 2026-11-16
Fix Fixed pam_usb (mcdope): 0.9.3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
mcdopepam_usb0.8.0 to before 0.9.30.9.3Patch availableCNA
  • pam_usb Vendormcdope Affected 0.8.0 to before 0.9.3 Fixed in 0.9.3 Patch available CNA

Remediation

Upgrade pam_usb to version 0.9.3, which fixes the issue. Versions before 0.8.0 are not listed as affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

  • Fix · CNA pam_usb (mcdope) Fixed in 0.9.3

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-64669
  2. 2026-11-12 Priority changed: MEDIUM → LOW
  3. 2026-11-14 CISA SSVC decision points changed

References

  • TI-2026-35505 pam_usb: PAM_RHOST check skipped when deny_remote=false allows XDMCP authentication bypass CVSS 3.1HIGH 8.1
  • TI-2026-32598 pam_usb: Symlink attacks on pad directory and pad files enable authentication bypass and root file corruption CVSS 3.1HIGH 7.9
  • TI-2026-32596 pam_usb: PINENTRY_FALLBACK_APP environment variable allows arbitrary command execution CVSS 3.1HIGH 7.8
  • TI-2026-32600 pam_usb: Command injection via $TMUX environment variable leads to RCE as root CVSS 3.1HIGH 8.8
  • TI-2026-32599 pam_usb: Shell injection via device UUID and username in pamusb-conf and pamusb-agent CVSS 3.1HIGH 8.2
  • TI-2026-89566 deny_remote bypass in pam_usb via IPv6 zone-indexed addresses CVSS 3.1HIGH 7.4
See all 25 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences