CVE-2026-39833

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

May 22, 2026

Last Modified

August 11, 2026

Advisory Details (6)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

GO-2026-5005 - Go Packages

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

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

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

Vendor Advisories for CVE-2026-39833(13)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulxd-tools (3.0.3-0ubuntu1~18.04.2+esm3) @ bionic2026-08-24ubuntu
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 rangeFixed inDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.10.0-1 ... 1:0.53.0-1 (33 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.53.0-1 (18 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.52.0-1~bpo13+1 (16 versions)1:0.52.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—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 7× in last 7d / 120× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 279 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-39833?
CVE-2026-39833 is a critical vulnerability 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 CVE-2026-39833 disclosed?
CVE-2026-39833 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39833 actively exploited?
CVE-2026-39833 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39833, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs