# GHSA-c7ph-f7jm-xv4w: rPGP's integrity protection of encrypted data was not always checked

> rPGP library fails to report invalid integrity protection during decryption, potentially exposing unverified data to applications relying on it.

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

## What is GHSA-c7ph-f7jm-xv4w?

GHSA-c7ph-f7jm-xv4w is a vulnerability in pgp, published on 13 Feb 2026. 

### Official description

### Summary
For some messages, rPGP returned incorrectly decrypted data without signaling that integrity protection was invalid.

### Details
When decrypting SEIPD (Symmetrically Encrypted and Integrity Protected Data Packet), rPGP previously did not under all circumstances report the absence of valid integrity protection to callers of the library.

### Impact
While the resulting invalid decryption output is not attacker controlled, its contents may be a security concern if an attacker can gain access to it.

### Attribution
Discovered internally in the course of rPGP development work.

## Which versions are affected by GHSA-c7ph-f7jm-xv4w?

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-c7ph-f7jm-xv4w?

Upgrade pgp to 0.19.0 or later.

## Is GHSA-c7ph-f7jm-xv4w being exploited?

There is no known exploitation of GHSA-c7ph-f7jm-xv4w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-c7ph-f7jm-xv4w and fix it if it is affected.

What it is: GHSA-c7ph-f7jm-xv4w is a vulnerability in pgp, published on 13 Feb 2026. 
Exploitation: There is no known exploitation of GHSA-c7ph-f7jm-xv4w 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-c7ph-f7jm-xv4w/ (Markdown: https://insights.sbomify.com/GHSA-c7ph-f7jm-xv4w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-c7ph-f7jm-xv4w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-c7ph-f7jm-xv4w/
Summaries are generated and may contain mistakes; the official description above is the record.