CVE-2026-64669
pam_usb: deny_remote bypassed by compressed IPv6 addresses in pusb_tmux_has_remote_clients
No exploitation reported by the sources we read.
- Published2026-11-11
- WeaknessCWE-285 · CWE-693
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-11-1103:52CVE publishedCNA
Versions per branch
Products declared by the CNA
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- mcdope pam_usbAffected
- = >= 0.8.0, < 0.9.3no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-11
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-64669 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2026-11-11
- Last Modified
- 2026-11-11
- NVD status
- Received
Frequently asked questions
What is CVE-2026-64669?
Is CVE-2026-64669 actively exploited?
What is the CVSS score for CVE-2026-64669?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
- CVE-2026-124194KEVsame week
- CVE-2026-125350KEVsame week
- CVE-2026-124580same week
- CVE-2026-124585same week
- CVE-2026-124577same week
- CVE-2026-125391same weekWebmin through 2.670 OS Command Injection via Samba User Account Options
- CVE-2026-125399same weekFluxion before 6.39 OS Command Injection via Crafted SSID
- CVE-2026-94434same weekOS Command Injection Leading to Root Code Execution in TÜBİTAK BİLGEM's Pardus Boot Repair