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.
Update golang.org/x/crypto to 0.52.0; golang.org/x/crypto/ssh/agent to 0.52.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scangolang.org/x/crypto/ssh/agent doesn't drop invoking agent constraints when forwarding keys affects golang.org/x/crypto (go), golang.org/x/crypto/ssh/agent (go). Severity is critical. 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.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/cryptogo |
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.
Update golang.org/x/crypto to 0.52.0; golang.org/x/crypto/ssh/agent to 0.52.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scangolang.org/x/crypto/ssh/agent doesn't drop invoking agent constraints when forwarding keys affects golang.org/x/crypto (go), golang.org/x/crypto/ssh/agent (go). Severity is critical. 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.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/cryptogo |
| <0.52.0 |
| 0.52.0 |
| golang.org/x/crypto/ssh/agentgo | <0.52.0 | 0.52.0 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| <0.52.0 |
| 0.52.0 |
| golang.org/x/crypto/ssh/agentgo | <0.52.0 | 0.52.0 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard