Skip to main content
VulnerabilityPublished Updated

CVE-2026-39828: golang.org/x/crypto/ssh · Incorrect Authorization

Affects golang.org/x/crypto/sshSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.52.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.52.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade golang.org/x/crypto/ssh to 0.52.0.

Affected software

ProductAffectedFixed in
golang.org/x/cryptogolang.org/x/crypto/sshAffected
  • <0.52.0
Fixed in
  • 0.52.0
Gogolang.org/x/crypto/sshpkg:golang/golang.org/x/crypto/sshOther threatsAffected
  • =0
Fixed in–
Gogolang.org/x/crypto/sshpkg:golang/golang.org/x/crypto/sshOther threatsAffected
  • <0.52.0
Fixed in
  • 0.52.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

According to the Red Hat advisory, no mitigation or fix currently meets their criteria for ease of use, deployment, applicability, or stability. If you cannot patch yet, consider limiting exposure of affected SSH servers and reviewing authentication callback configurations to avoid returning PartialSuccessError with non-nil permissions if possible. Engage with Red Hat support or technical account managers for tailored guidance.

Description

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.

References

Community reviews

Loading reviews…