Skip to content
Threat Brief

← All advisories

CVE-2026-76088

High 7.5No known exploitationFix available

PGPainless: Unbounded Compressed Packet Descent in inline-detach and MessageInspector leads to Denial of Service (DoS)

Vendor advisory: GHSA-cvx8-9ff6-54xq

Record last updated

CVSS score

7.5

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 55% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-400

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mavenorg.pgpainless:pgpainless-corefrom 2.0.0 before 2.0.42.0.4GitHub Advisory Database
mavenorg.pgpainless:pgpainless-coreall versions before 1.7.81.7.8GitHub Advisory Database
pgpainlesspgpainless< 1.7.8Not documentedCVE Program
pgpainlesspgpainless>= 2.0.0, < 2.0.4Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references