CVE-2026-39833

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. 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 NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated 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 in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.

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

August 11, 2026

Advisory Details (6)

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

GO-2026-5005 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5005
Web page
https://groups.google.com/g/golang-announce/c/a082jnz-LvI
Web page

x/crypto/ssh/agent: `lifetime` without `confirm` constraint · Issue #79436 · golang/go · GitHub

https://go.dev/issue/79436
Web page
https://go.dev/cl/778642
Web page
https://go.dev/cl/778641
Web page
https://go.dev/cl/778640

Vendor Advisories for CVE-2026-39833(16)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulxd-tools (3.0.3-0ubuntu1~18.04.2+esm3) @ bionic2026-10-14ubuntu
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17836121632026-07-16redhat
redhatrhtas/gitsign-rhel9:17833320612026-07-09redhat
redhatconforma-cli-stack-v1-4-1.4.22026-07-09redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17830582842026-07-08redhat

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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-39833?
CVE-2026-39833 is a critical-severity vulnerability; its CVE record was published on May 22, 2026. The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when…
When was the CVE record for CVE-2026-39833 published?
The CVE record for CVE-2026-39833 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 August 11, 2026; the record at its source may have been updated since.
Is CVE-2026-39833 actively exploited?
CVE-2026-39833 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-39833?
CVE-2026-39833 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-39833?
A fix for CVE-2026-39833 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39833 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-39833

Explore →

Is Your Infrastructure Affected by CVE-2026-39833?

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

Book a Demo →Browse All CVEs