# GHSA-8h58-w33p-wq3g: rPGP affected by crash in message handling for deeply nested messages

> An attacker can cause a denial of service by sending deeply nested PGP messages that trigger a stack overflow in the rPGP library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2026

## What is GHSA-8h58-w33p-wq3g?

GHSA-8h58-w33p-wq3g is a denial of service vulnerability in pgp, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary
Previous rPGP versions could be caused to crash with a "stack overflow" when parsing messages that contain deeply nested message layers, such as messages with many signatures.

rPGP 0.19.0 resolves this issue with a more robust message handling implementation (via https://github.com/rpgp/rpgp/pull/625).

### Impact
An attacker could cause applications to crash in rPGP's message parsing subsystem, when applications attempt to ingest messages.

### Attribution
Discovered internally during rPGP development, using a fuzz test suite previously contributed by Christian Reitter.

## Which versions are affected by GHSA-8h58-w33p-wq3g?

2 open source packages ship an affected version, including pgp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pgp` | crates.io | From 0.16.0-alpha.0 | 0.19.0 |
| `pgp` | crates.io | From 0.16.0-alpha.0 | 0.19.0 |

## How do I fix GHSA-8h58-w33p-wq3g?

Upgrade pgp to 0.19.0 or later.

## Is GHSA-8h58-w33p-wq3g being exploited?

There is no known exploitation of GHSA-8h58-w33p-wq3g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8h58-w33p-wq3g and fix it if it is affected.

What it is: GHSA-8h58-w33p-wq3g is a denial of service vulnerability in pgp, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8h58-w33p-wq3g in the wild and no public exploit code.

Affected packages and fixed versions:
- pgp (crates.io): affected from 0.16.0-alpha.0; fixed in 0.19.0
- pgp (crates.io): affected from 0.16.0-alpha.0; fixed in 0.19.0

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/GHSA-8h58-w33p-wq3g/ (Markdown: https://insights.sbomify.com/GHSA-8h58-w33p-wq3g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8h58-w33p-wq3g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8h58-w33p-wq3g/
Summaries are generated and may contain mistakes; the official description above is the record.