CVE-2026-39831

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — Patch released this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available.
Web page

GO-2026-5019 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5019
Web page

x/crypto/ssh: bypass of FIDO/U2F security keys physical interaction · Issue #79566 · golang/go · GitHub

https://go.dev/issue/79566

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-docker-builder-rhel9:17906331932026-10-08redhat
redhatopenshift4/ose-docker-builder-rhel9:17906101592026-10-07redhat
redhatcompliance/openshift-security-profiles-rhel8-operator:17906230302026-10-06redhat
redhatrhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9:17901301732026-09-30redhat
redhatopenshift4/ose-docker-builder-rhel9:17898853242026-09-29redhat
redhatopenshift4/ose-docker-builder-rhel9:17899877772026-09-29redhat
redhatmulticluster-engine/azure-service-operator-rhel9:17901335432026-09-28redhat
redhatopenshift-logging/cluster-logging-rhel9-operator:17896591662026-09-23redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17894654142026-09-22redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatrhem/flightctl-worker-rhel9:17894868292026-09-16redhat
redhatrhem/flightctl-worker-rhel10:17894860712026-09-16redhat
redhatflightctl-0:1.1.4-1.el9em2026-09-16redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17889289032026-09-15redhat
redhatpodman-5:5.4.0-22.el9_6.52026-09-14redhat
redhatopenshift-logging/cluster-logging-rhel9-operator:17884395052026-09-10redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatdevspaces/traefik-rhel9:17877567992026-09-01redhat
redhatcluster-observability-operator/cluster-observability-rhel9-operator:17875936372026-08-31redhat
redhatrhoai/odh-trainer-rhel9:17870890492026-08-27redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17872640682026-08-25redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17869553162026-08-25redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17872591132026-08-25redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17864759642026-08-25redhat
redhatoadp/oadp-velero-rhel9:17869445402026-08-25redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatopenshift4/ose-machine-api-provider-azure-rhel9:17865497592026-08-18redhat
redhatrhacm2/volsync-rhel9:17864566582026-08-12redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17865483812026-08-12redhat
redhatquay/quay-rhel9:17861819812026-08-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.10.0-1 ... 1:0.56.0-1 (36 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.56.0-1 (21 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.52.0-1~bpo13+1 (16 versions)
  • every version up to 1:0.52.0-1: fixed in 1:0.52.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/crypto—
  • every version up to 0.52.0: fixed in 0.52.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 274 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 175 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-14 11:17 UTCEG score recompute
  3. 2026-10-14 11:17 UTCVendor advisory
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-13 09:42 UTCEG score recompute
  6. 2026-10-13 09:42 UTCVendor advisory
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-12 16:10 UTCEG score recompute
  9. 2026-10-12 08:09 UTCVendor advisory
  10. 2026-10-11 19:52 UTCEG score recompute
  11. 2026-10-11 17:05 UTCEG score recompute
  12. 2026-10-11 14:32 UTCEG score recompute
  13. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-30 10:17 UTCOSV refresh
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 74 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-09-11 17:23 UTCOSV refresh
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-08-23 20:59 UTCVendor advisory
  30. 2026-08-23 16:42 UTCEG score recompute
  31. 2026-08-23 16:42 UTCVendor advisory
  32. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-08-22 01:59 UTCEG score recompute
  34. 2026-08-22 01:59 UTCVendor advisory
  35. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-08-21 21:42 UTCEG score recompute
  37. 2026-08-21 21:42 UTCVendor advisory
  38. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-08-20 18:40 UTCEG score recompute
  40. 2026-08-20 18:40 UTCVendor advisory
  41. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-08-17 14:02 UTCEG score recompute
  44. 2026-08-17 14:02 UTCVendor advisory
  45. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-08-17 09:45 UTCVendor advisory
  47. 2026-08-16 16:49 UTCEG score recompute
  48. 2026-08-16 16:49 UTCVendor advisory
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  50. 2026-08-16 11:54 UTCVendor advisory
  51. 2026-08-16 07:37 UTCVendor advisory
  52. 2026-08-16 03:21 UTCEG score recompute
  53. 2026-08-16 03:21 UTCVendor advisory
  54. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-08-15 03:41 UTCEG score recompute
  56. 2026-08-15 03:41 UTCVendor advisory
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-08-14 23:19 UTCVendor advisory
  59. 2026-08-14 19:02 UTCVendor advisory
  60. 2026-08-14 14:45 UTCVendor advisory
  61. 2026-08-14 10:28 UTCVendor advisory
  62. 2026-08-14 06:11 UTCVendor advisory
  63. 2026-08-14 01:54 UTCEG score recompute
  64. 2026-08-14 01:54 UTCVendor advisory
  65. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  66. 2026-08-13 08:04 UTCVendor advisory
  67. 2026-08-13 03:03 UTCVendor advisory
  68. 2026-08-12 22:46 UTCVendor advisory
  69. 2026-08-12 18:30 UTCVendor advisory
  70. 2026-08-12 14:13 UTCEG score recompute
  71. 2026-08-12 14:13 UTCVendor advisory
  72. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  73. 2026-08-12 09:50 UTCVendor advisory
  74. 2026-08-11 22:54 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-39831?
CVE-2026-39831 is a critical-severity vulnerability; its CVE record was published on May 22, 2026. 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,…
When was the CVE record for CVE-2026-39831 published?
The CVE record for CVE-2026-39831 was published on May 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-39831 actively exploited?
CVE-2026-39831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39831?
CVE-2026-39831 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-39831?
A fix for CVE-2026-39831 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39831 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39831

Explore →

Is Your Infrastructure Affected by CVE-2026-39831?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.