Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The golang.org/x/crypto module, versions before 0.52.0, has a flaw in the in-memory keyring returned by NewKeyring(): it accepts keys with the ConfirmBeforeUse constraint but does not enforce it, so keys can sign without the expected confirmation prompt. The source gives few details on how an attacker would reach this keyring. Upgrade to golang.org/x/crypto 0.52.0 or later, where NewKeyring() returns an error when unsupported constraints are requested.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0047, the 41st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV