Skip to content
Fencer Intel
no cvss —

GO-2026-5932 json

The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues

published 4mo ago modified 9d ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used.

If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.

Patch / fix

  • go golang.org/x/crypto 0.58.1-0.20261009181718-2f1f834330b2

Is GO-2026-5932 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go golang.org/x/crypto
<0.58.1-0.20261009181718-2f1f834330b2
0.58.1-0.20261009181718-2f1f834330b2
go golang.org/x/crypto/openpgp
all versions
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.