Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassedGHSA-89gr-r52h-f8rx

CRITICAL

GHSA-89gr-r52h-f8rx is a critical-severity (CVSS 9.1) CWE-862 vulnerability in golang.org/x/crypto. A fix is available for golang.org/x/crypto — see the affected versions and patch details below.

Also known asCVE-2026-39831GO-2026-5019
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-89gr-r52h-f8rx.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk-0.01%
Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk
0.00%0.33%0.66%0.99%0.0%0.5%Jun 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-89gr-r52h-f8rx by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,308 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐹golang.org/x/crypto

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The 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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogolang.org/x/cryptoall versions0.52.0go get golang.org/x/crypto@v0.52.0

Affected Products

1 product · 1 configurations
Application
cryptogolang
< 0.52.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update golang.org/x/crypto to 0.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-89gr-r52h-f8rx is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat Enterprise Linux 9.6 Extended Update Supportpodman-5:5.4.0-22.el9_6.5RHSA-2026:67450
RHEM 1.1 for RHEL 10flightctl-0:1.1.4-1.el10emRHSA-2026:68334
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791371080RHSA-2026:82304
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/cert-manager-operator-rhel9:1791788287RHSA-2026:82322
Cluster Observability Operator 1.5.3cluster-observability-operator/cluster-observability-rhel9-operator:1787593637RHSA-2026:61314
Logging Subsystem for Red Hat OpenShift 6.5openshift-logging/cluster-logging-rhel9-operator:1789659166RHSA-2026:70870
Logging Subsystem for Red Hat OpenShift 6.6openshift-logging/cluster-logging-rhel9-operator:1788439505RHSA-2026:66521
multicluster engine for Kubernetes 2.10multicluster-engine/hypershift-addon-rhel9-operator:1786548381RHSA-2026:54432
UbuntuCRITICAL
USN-8447-3Ubuntu

Frequently Asked Questions

The 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.
O3 Security · Impact-Aware SCA

Is GHSA-89gr-r52h-f8rx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
golang.org/x/crypto: FIDO/U2F security key physical…