CVE-2026-39832
Description
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.
How to fix
- golang crypto0.52.0 or later
- golang.org/x/crypto0.52.0 or later
- access.redhat.com/errata/RHSA-2026:41019
- access.redhat.com/errata/RHSA-2026:36796
- access.redhat.com/errata/RHSA-2026:36199
- access.redhat.com/errata/RHSA-2026:37072
- access.redhat.com/errata/RHSA-2026:35833
- access.redhat.com/errata/RHSA-2026:49944
- access.redhat.com/errata/RHSA-2026:67450
- access.redhat.com/errata/RHSA-2026:37410
- access.redhat.com/errata/RHSA-2026:37123
- access.redhat.com/errata/RHSA-2026:61314
- access.redhat.com/errata/RHSA-2026:66521
- access.redhat.com/errata/RHSA-2026:43692
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| golang crypto | v < 0.52.0 | 0.52.0 |
| golang.org/x/cryptoGo | v < 0.52.0 | 0.52.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.