Skip to main content
VulnerabilityPublished Updated

CVE-2026-39832: golang.org/x/crypto/ssh/agent · Improper Preservation of Permissions

Affects golang.org/x/crypto/ssh/agentSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.52.0 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% 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:N/UI:N/S:U/C:H/I:H/A:N

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 29 Oct 2026.

What to do

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

Affected software

ProductAffectedFixed in
golang.org/x/cryptogolang.org/x/crypto/ssh/agentAffected
  • <0.52.0
Fixed in
  • 0.52.0
Gogolang.org/x/crypto/ssh/agentpkg:golang/golang.org/x/crypto/ssh/agentOther threatsAffected
  • =0
Fixed in–
Gogolang.org/x/crypto/ssh/agentpkg:golang/golang.org/x/crypto/ssh/agentOther 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 patch currently meets their criteria for ease of use, deployment, applicability, or stability. If you cannot patch yet, users relying on constraint extensions for limiting SSH key usage should exercise caution when forwarding keys via SSH agents. Engage with Red Hat support or Technical Account Managers for guidance specific to your environment.

Description

When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.

References

Community reviews

Loading reviews…