CVE-2026-39832: Go x/crypto Insecure Deserialization

CVE-2026-39832 is a critical insecure deserialization vulnerability in Go x/crypto, published in the National Vulnerability Database (NVD) on May 22, 2026. It carries a CVSS v3.1 base score of 9.1 (Critical). According to its CVSS vector, it can be exploited over the network, needs no privileges and no user interaction.

What is CVE-2026-39832?

Exploiting key forwarding in OpenSSH could allow unrestricted key usage.

The NVD description reads:

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.

NVD maps this issue to CWE-502 (Deserialization of Untrusted Data), CWE-281 (Improper Preservation of Permissions).

Affected versions and packages

NVD's CPE configuration lists these vulnerable version ranges:

• crypto before 0.52.0

Based on those ranges, the first versions that are no longer listed as vulnerable include: 0.52.0.

Echo's advisory data tracks 1 package for CVE-2026-39832: golang.org/x/crypto.

Package versions listed in Echo's advisory data for this CVE (compare them with the versions you run):

• golang.org/x/crypto: v0.49.0

Severity and CVSS score

A score of 9.1 puts CVE-2026-39832 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to managing Docker vulnerability risk.

Impact: Insecure Deserialization

The CVSS vector rates the impact on confidentiality as high, integrity as high and availability as none. Exploitation requires no privileges and no user interaction, and the attacker reaches the target over the network.

What this means in practice depends on how Go x/crypto is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.

Is CVE-2026-39832 being exploited in the wild?

As of November 4, 2026, CVE-2026-39832 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). That is not proof that it is not being exploited. Its EPSS value in Echo's advisory data is 0.53, so use that together with exposure and CVSS severity to set a patch deadline.

How to fix CVE-2026-39832

1. Inventory. Find every host, container image and base image that includes Go x/crypto, including the packages listed above (golang.org/x/crypto).
2. Upgrade. Upgrade to 0.52.0 or later, the first versions that NVD no longer lists as vulnerable, or to the version your distribution or vendor lists as fixed.
3. Rebuild and restart. Rebuild container images and restart the services that load Go x/crypto so the patched code is actually used.
4. Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2026-39832.

Interim mitigations if you cannot patch immediately

These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.

• Restrict network access to services that use Go x/crypto to trusted sources with firewall rules or allow-lists until you can patch.
• Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.

How Echo helps with CVE-2026-39832

Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 1 package (golang.org/x/crypto). Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters. Related Go advisories: CVE-2026-39821 and CVE-2026-42508.

Frequently asked questions about CVE-2026-39832

What is CVE-2026-39832?

CVE-2026-39832 is a critical insecure deserialization vulnerability in Go x/crypto. Exploiting key forwarding in OpenSSH could allow unrestricted key usage. It has a CVSS base score of 9.1.

Which versions are affected by CVE-2026-39832?

NVD lists these vulnerable ranges: crypto before 0.52.0.

Is CVE-2026-39832 actively exploited?

It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. Its EPSS value in Echo's advisory data is 0.53.

How do I fix CVE-2026-39832?

Upgrade to 0.52.0 or later, the first versions that NVD no longer lists as vulnerable, or to the version your distribution or vendor lists as fixed. Then rebuild images, restart affected services and re-scan to confirm the fix.

How severe is CVE-2026-39832?

It is rated Critical with a CVSS base score of 9.1. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N means it can be exploited over the network, with no privileges and no user interaction.

Are there other Go vulnerabilities I should patch?

Yes. Echo's advisory data also covers CVE-2026-39821 and CVE-2026-42508. Patch them together to reduce the number of upgrade cycles.