CVE-2026-39828

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd 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 — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 18, 2026

Advisory Details (4)

Auto-updated Jun 14, 2026
Patch available.
Web page

GO-2026-5014 - Go Packages

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

x/crypto/ssh: bypass of certificate restrictions · Issue #79562 · golang/go · GitHub

https://go.dev/issue/79562

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-logging/cluster-logging-rhel9-operator:17884395052026-09-10redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatrhoai/odh-trainer-rhel9:17870890492026-08-27redhat
redhatoadp/oadp-velero-rhel9:17869445402026-08-25redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17869119572026-08-19redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17869087772026-08-19redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17866138052026-08-13redhat
redhatopenshift4/ose-hyperkube-rhel9:17858846882026-08-11redhat
redhatopenshift-gitops-1/argocd-rhel9:17852113462026-08-10redhat
redhatopenshift-gitops-1/argocd-rhel8:17851492602026-08-10redhat
redhatoadp/oadp-velero-rhel9:17851808782026-08-06redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-192026-07-29redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17846467862026-07-29redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17846460262026-07-28redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17842295082026-07-28redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhtas/rekor-cli-rhel9:17839693652026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17830258202026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatrhem/flightctl-worker-rhel10:17841949712026-07-16redhat
redhatrhtas/timestamp-authority-rhel9:17839686442026-07-16redhat

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(2)

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

Frequently asked(5)

What is CVE-2026-39828?
CVE-2026-39828 is a medium-severity vulnerability; its CVE record was published on May 22, 2026. When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError…
When was the CVE record for CVE-2026-39828 published?
The CVE record for CVE-2026-39828 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 September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-39828 actively exploited?
CVE-2026-39828 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39828?
CVE-2026-39828 has a CVSS v3.1 base score of 6.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-39828?
A fix for CVE-2026-39828 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39828 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-39828

Explore →

Is Your Infrastructure Affected by CVE-2026-39828?

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