CVE-2026-39833
Golang Crypto broken access control
- Published22 May 2026
Description
The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-39833 being actively exploited?
CVE-2026-39833 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.
How severe is CVE-2026-39833?
CVE-2026-39833 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.49% probability of exploitation.
Which products are affected by CVE-2026-39833?
Affected products include Golang Crypto.
How do I fix CVE-2026-39833?
Upgrade affected software to a fixed version, for example Golang Crypto 0.52.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-39833 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.