CVE-2025-29991
First published: Thu Apr 03 2025(Updated: )
Yubico YubiKey 5.4.1 through 5.7.3 before 5.7.4 has an incorrect FIDO CTAP PIN/UV Auth Protocol Two implementation. It uses the signature length from CTAP PIN/UV Auth Protocol One, even when CTAP PIN/UV Auth Protocol Two was chosen, resulting in a partial signature verification.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Yubico YubiKey | >=5.4.1<=5.7.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-29991?
CVE-2025-29991 is classified as a medium severity vulnerability due to its impact on signature verification.
How do I fix CVE-2025-29991?
To mitigate CVE-2025-29991, upgrade your YubiKey firmware to version 5.7.4 or later.
What versions of YubiKey are affected by CVE-2025-29991?
YubiKey versions 5.4.1 through 5.7.3 are affected by CVE-2025-29991.
What is the impact of CVE-2025-29991 on YubiKey users?
CVE-2025-29991 can lead to improper signature verification during authentication, potentially compromising security.
Is there a workaround for CVE-2025-29991?
There are no known workarounds for CVE-2025-29991, making firmware upgrade the recommended solution.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/source
- agent/severity
- agent/tags
- agent/author
- agent/last-modified-date
- agent/event
- vendor/yubico
- canonical/yubico yubikey