CVE-2026-76088

7.5High

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.5CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on availability
Weakness
CWE-400

What an attacker gets

Unauthenticated attackers can crash your application by sending deeply nested PGP packets. This triggers excessive resource consumption that exhausts heap memory and blocks processing threads.

Root cause

The code fails to enforce a maximum nesting depth when decompressing PGP packets, allowing for recursive resource exhaustion.

Affected versions

PGPainless versions prior to 1.7.8 and 2.0.0 through 2.0.3.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Fix & remediation

Upgrade to PGPainless version 1.7.8 or 2.0.4. If you cannot patch immediately, implement a size limit on incoming PGP messages to prevent processing of excessively large or complex payloads.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

PGPainless is a simple-to-use OpenPGP API based on Bouncy Castle. Prior to 1.7.8 and from 2.0.0 until 2.0.4, pgpainless-sop/src/main/kotlin/org/pgpainless/sop/InlineDetachImpl.kt InlineDetachImpl and pgpainless-core/src/main/kotlin/org/pgpainless/decryption_verification/MessageInspector.kt MessageInspector manually descend PGPCompressedData packets without incrementing or enforcing MAX_LAYER_DEPTH. A remote unauthenticated attacker can supply an untrusted OpenPGP message containing deeply nested compressed packet structures to a downstream application using inline-detach or message inspection, bypass the intended 16-layer limit, and force continued decompression and packet processing. The resulting resource consumption can block processing threads, exhaust heap memory, and crash the consuming application. This issue is fixed in versions 1.7.8 and 2.0.4.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-76088