Quick answers
- Is CVE-2026-47269 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47269 being exploited in the wild.
- How severe is CVE-2026-47269?
- High severity, with a CVSS score of 7.4, published 27 May 2026.
- Which products and versions are affected?
- Mcdope Pam Usb < 0.9.0.
- Is there a fix for CVE-2026-47269?
- A patch was published on 2026-05-27: Fixed in version 0.9.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47269 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47269?
- 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 vulnerability exists in pam_usb's 'deny_remote' feature due to an incomplete check of the utmpx ut_addr_v6 field. The software originally only validated the first 32-bit word of the 128-bit IPv6 address field to detect remote sessions. Because IPv4-mapped IPv6 addresses (::ffff:x.x.x.x) store the address data in the final word and leave the first word as zero, remote connections on systems using IPv6 wildcards (common in Debian/Ubuntu SSH configurations) are misclassified as local. An attacker with physical access to a registered USB device can exploit this to authenticate via SSH, bypassing the intended remote-access block. This issue is resolved in version 0.9.0 by ensuring all four words of the address field are checked.
Affected products
- mcdope pam_usb < 0.9.0
Timeline
- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-05-27: disclosed: CVE-2026-47269 published to NVD
- 2026-05-27: patched: Fixed in version 0.9.0