Invoking bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh
cve-program · CVE-2026-39831
PublishedThe Verify() method for FIDO/U2F security key types ([email protected], [email protected]) 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.
Read the publisher's advisoryeuvd · EUVD-2026-31395
PublishedThe Verify() method for FIDO/U2F security key types ([email protected], [email protected]) 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.
Read the publisher's advisorynvd · CVE-2026-39831
PublishedThe Verify() method for FIDO/U2F security key types ([email protected], [email protected]) 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.
Read the publisher's advisoryosv · GHSA-89gr-r52h-f8rx
PublishedThe Verify() method for FIDO/U2F security key types ([email protected], [email protected]) 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.
Read the publisher's advisoryosv · GO-2026-5019
PublishedThe Verify() method for FIDO/U2F security key types ([email protected], [email protected]) 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-39831 · CVE overview and exploitation status
cve-program · CVE-2026-39831
- https://go.dev/issue/79566
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://go.dev/cl/781662
- https://pkg.go.dev/vuln/GO-2026-5019
euvd · EUVD-2026-31395
- https://go.dev/issue/79566
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://go.dev/cl/781662
- https://pkg.go.dev/vuln/GO-2026-5019
nvd · CVE-2026-39831
- https://go.dev/cl/781662
- https://go.dev/issue/79566
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5019
osv · GHSA-89gr-r52h-f8rx
- https://nvd.nist.gov/vuln/detail/CVE-2026-39831
- https://cs.opensource.google/go/x/crypto
- https://go.dev/cl/781662
- https://go.dev/issue/79566
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5019