CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NCVE-2026-64669 pam_usb: deny_remote bypassed by compressed IPv6 addresses in pusb_tmux_has_remote_clients
High (7.4) in mcdope pam usb. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- OWASP Top 10
- A01:2025 Broken Access Control, A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-64669 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64669?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64669?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64669 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-64669)
HTML:
<a href="https://cve.bz/cve/CVE-2026-64669"><img src="https://cve.bz/cve/badge/CVE-2026-64669.svg" alt="CVE-2026-64669"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| mcdope pam_usb | >= 0.8.0, < 0.9.3 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16), CWE-693 (17).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.