An information leak was discovered on Yubico YubiKey 5 NFC devices 5.0.0 to 5.2.6 and…
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-862.
Summary
An information leak was discovered on Yubico YubiKey 5 NFC devices 5.0.0 to 5.2.6 and 5.3.0 to 5.3.1. The OTP application allows a user to set optional access codes on OTP slots. This access code is intended to prevent unauthorized changes to OTP configurations. The access code is not checked when updating NFC specific components of the OTP configurations. This may allow an attacker to access configured OTPs and passwords stored in slots that were not configured by the user to be read over NFC, despite a user having set an access code. (Users who have not set an access code, or who have not configured the OTP slots, are not impacted by this issue.)
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2020-15001
- 2026-10-03 Alias added: GHSA-9wfp-32vx-wv8g
References
More Yubico Yubikey 5 Nfc Firmware vulnerabilities
- TI-2020-11792 A PIN management problem was discovered on Yubico YubiKey 5 devices 5.2.0 to 5.2.6. CVSS 3.1MEDIUM 5.9
- TI-2024-30675 Yubico YubiKey 5 Series devices with firmware before 5.7.0 and YubiHSM 2 devices with… CVSS 3.1MEDIUM 4.2
Sources
- CVE-2020-15001 · CVE Program
- CVE-2020-15001 · NVD
- FIRST EPSS
- GHSA-9wfp-32vx-wv8g · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences