For some messages, rPGP returned incorrectly decrypted data without signaling that integrity protection was invalid.
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.
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.
Discovered internally in the course of rPGP development work.
{
"cwe_ids": [
"CWE-354"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-13T20:55:20Z",
"nvd_published_at": null,
"severity": "MODERATE"
}