CVE-2026-39832: golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys
When adding a key to a remote agent constraint extensions such as [email protected] 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.
Published Jun 25, 2026 · Updated Aug 11, 2026
Affected packages
golang.org/x/crypto
- Ecosystem
- Go
- Affected
- < 0.52.0
- Fixed in
- 0.52.0
- Check
go list -m golang.org/x/crypto
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
When adding a key to a remote agent constraint extensions such as [email protected] 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
- https://nvd.nist.gov/vuln/detail/CVE-2026-39832
- https://go.dev/cl/778642
- https://go.dev/issue/79435
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5006
- https://access.redhat.com/security/cve/CVE-2026-39832
- https://bugzilla.redhat.com/show_bug.cgi?id=2480685
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-39832.json
- https://access.redhat.com/errata/RHSA-2026:35833
- https://access.redhat.com/errata/RHSA-2026:36199
- https://access.redhat.com/errata/RHSA-2026:36319
- https://access.redhat.com/errata/RHSA-2026:36625
- https://access.redhat.com/errata/RHSA-2026:36648
- https://access.redhat.com/errata/RHSA-2026:37271
- https://access.redhat.com/errata/RHSA-2026:37123
- https://access.redhat.com/errata/RHSA-2026:37072
- https://access.redhat.com/errata/RHSA-2026:36797
- https://access.redhat.com/errata/RHSA-2026:36796
- https://access.redhat.com/errata/RHSA-2026:36651
- https://access.redhat.com/errata/RHSA-2026:37410
- https://access.redhat.com/errata/RHSA-2026:37387
- https://access.redhat.com/errata/RHSA-2026:40262
- https://access.redhat.com/errata/RHSA-2026:40118
- https://access.redhat.com/errata/RHSA-2026:41066
- https://access.redhat.com/errata/RHSA-2026:41036
- https://access.redhat.com/errata/RHSA-2026:41031
- https://access.redhat.com/errata/RHSA-2026:41019
- https://access.redhat.com/errata/RHSA-2026:40972
- https://access.redhat.com/errata/RHSA-2026:40945
- https://access.redhat.com/errata/RHSA-2026:42146
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-39830
golang.org/x/crypto: Invoking client can cause server deadlock on unexpected responses
critical9.1Jun 25, 2026CVE-2026-39831
golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed
critical9.1Jun 25, 2026CVE-2026-39833
golang.org/x/crypto doesn't enforce invoking key constraints
critical9.1Jun 25, 2026CVE-2026-39834
golang.org/x/crypto vulnerable to infinite loop on large channel writes
critical9.1Jun 25, 2026CVE-2026-42508
golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status
critical9.1Jun 25, 2026CVE-2026-46595
golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement
critical10.0Jun 25, 2026
