# GO-2026-5932: The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues

> The golang.org/x/crypto/openpgp package is unmaintained and unsafe by design, requiring users to migrate to a maintained fork.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Jul 2026

## What is GO-2026-5932?

GO-2026-5932 is a vulnerability in golang.org/x/crypto, published on 7 Jul 2026. 

### Official description

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.

## Which versions are affected by GO-2026-5932?

1 open source package ship an affected version, including golang.org/x/crypto.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang.org/x/crypto` | Go | All versions | None |

## How do I fix GO-2026-5932?

No fix has been published for GO-2026-5932 yet. Limit exposure of the affected software until one is available.

## Is GO-2026-5932 being exploited?

There is no known exploitation of GO-2026-5932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GO-2026-5932 and fix it if it is affected.

What it is: GO-2026-5932 is a vulnerability in golang.org/x/crypto, published on 7 Jul 2026. 
Exploitation: There is no known exploitation of GO-2026-5932 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang.org/x/crypto (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GO-2026-5932/ (Markdown: https://insights.sbomify.com/GO-2026-5932/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GO-2026-5932

---
From sbomify Insights: https://insights.sbomify.com/GO-2026-5932/
Summaries are generated and may contain mistakes; the official description above is the record.