Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-39831: The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openss

52
This month
CRITICAL 9.1REMOTEWATCHLISTUPGRADE

CVE-2026-39831 is a critical-severity flaw (CVSS 9.1) affecting crypto. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 59%)
CISA exploited listNo
WeaknessCWE-862
Published2026-05-22
Last modified2026-07-23
Publisher (CNA): Go Project · Vendor: golang

Share: LinkedIn · X · Reddit

Last updated 2026-07-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

golang crypto UPGRADE
Affected: < 0.52.0
Fixed in: 0.52.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy crypto || rpm -q crypto || crypto --version
2. UPGRADE to 0.52.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade crypto
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade crypto
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39831?

crypto: upgrade to 0.52.0. Exact commands for each OS are on this page.

Is CVE-2026-39831 being exploited?

CVE-2026-39831 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39831 affect?

CVE-2026-39831 affects crypto. Severity is critical (CVSS 9.1). 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

How urgent is CVE-2026-39831?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

OpenSSH vulnerabilities · Go (Golang) vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.