Advisory record · GHSA-jppx-rxg9-jmrx

golang.org/x/crypto doesn't enforce invoking key constraints

CVSS 9.1 CriticalCriticalEPSS 0.0047 · 41st percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 25 Jun 2026, 22:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
golang.org/x/cryptoGo<0.52.00.52.0
Identifiers
GHSA-jppx-rxg9-jmrx · CVE-2026-39833 · GO-2026-5005
Weakness (CWE)
CWE-862
Published
25 Jun 2026
Updated
10 Sept 2026

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.

Written 1 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.