CVE-2026-39831: CWE-290: Authentication Bypass by Spoofing in golang.org/x/crypto golang.org/x/crypto/ssh
The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.
AI Analysis
Technical Summary
The golang.org/x/crypto/ssh package contains a vulnerability in its Verify() method for FIDO/U2F security keys (specifically sk-ecdsa-sha2-nistp256@openssh.com and sk-ssh-ed25519@openssh.com). The method does not verify the User Presence flag, which is intended to require physical user interaction (touch) on the hardware key. As a result, signatures generated without this physical touch are accepted, enabling potential unauthorized use of the hardware security key without user presence. The vulnerability allows bypassing authentication controls relying on physical user presence. The recommended workaround is to explicitly return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback to restore prior behavior. No official patch or fix has been documented yet.
Potential Impact
This vulnerability allows an attacker or automated process to use a hardware security key without requiring physical user presence, effectively bypassing a security control designed to prevent unattended use. This could lead to unauthorized authentication if an attacker gains access to the system or key. However, there are no known exploits in the wild at this time. The impact is limited to scenarios relying on the affected Verify() method for enforcing user presence with FIDO/U2F keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the meantime, users can mitigate the issue by returning a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback to restore the previous behavior that enforces user presence. Monitor official golang.org/x/crypto advisories for updates and patches.
CVE-2026-39831: CWE-290: Authentication Bypass by Spoofing in golang.org/x/crypto golang.org/x/crypto/ssh
Description
The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The golang.org/x/crypto/ssh package contains a vulnerability in its Verify() method for FIDO/U2F security keys (specifically sk-ecdsa-sha2-nistp256@openssh.com and sk-ssh-ed25519@openssh.com). The method does not verify the User Presence flag, which is intended to require physical user interaction (touch) on the hardware key. As a result, signatures generated without this physical touch are accepted, enabling potential unauthorized use of the hardware security key without user presence. The vulnerability allows bypassing authentication controls relying on physical user presence. The recommended workaround is to explicitly return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback to restore prior behavior. No official patch or fix has been documented yet.
Potential Impact
This vulnerability allows an attacker or automated process to use a hardware security key without requiring physical user presence, effectively bypassing a security control designed to prevent unattended use. This could lead to unauthorized authentication if an attacker gains access to the system or key. However, there are no known exploits in the wild at this time. The impact is limited to scenarios relying on the affected Verify() method for enforcing user presence with FIDO/U2F keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the meantime, users can mitigate the issue by returning a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback to restore the previous behavior that enforces user presence. Monitor official golang.org/x/crypto advisories for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Go
- Date Reserved
- 2026-04-07T18:13:03.528Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0fcdabe1370fbb487d5010
Added to database: 5/22/2026, 3:29:47 AM
Last enriched: 5/22/2026, 3:45:26 AM
Last updated: 5/23/2026, 11:12:36 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.