Skip to main content
Menu
CVEs

CVE

PGPainless denial of service in nested compressed packet parsing

Affects pgpainless-core 1.7.7 and earlier and 2.0.0 through 2.0.3 when the application uses the inline-detach (SOP) or MessageInspector code paths on untrusted input. Fixed in 1.7.8 and 2.0.4.

CVE-2026-76088Published Updated Summary written by a model

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.7.8, 2.0.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.7.8, 2.0.4.

Summary

The PGPainless OpenPGP library, used through its inline-detach and message inspection features, fails to enforce its limit on nested compressed packets. A remote attacker who can supply an OpenPGP message without logging in can make the consuming application keep decompressing and processing packets, which can exhaust memory and crash it.

Original 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.

Who should check

Teams using pgpainless-core 1.7.7 or earlier, or 2.0.0 to 2.0.3, that run inline-detach or MessageInspector on untrusted OpenPGP input, such as gateways or mail clients.

“Affected versions <= 1.7.7, 2.0.0, 2.0.1, 2.0.2, 2.0.3”

github.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.7.8, 2.0.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-76088 (PGPainless: Unbounded Compressed Packet Descent in inline-detach and MessageInspector leads to Denial of Service (DoS)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76088 (entry last updated 2026-11-18):
Affected:
- pgpainless pgpainless: fixed in 1.7.8; from 2.0.0, fixed in 2.0.4
Fixed versions: 1.7.8, 2.0.4.
Conditions (all must be true for the bug to be hit):
- Affects pgpainless-core 1.7.7 and earlier, and 2.0.0 through 2.0.3. (source: https://github.com/pgpainless/pgpainless/security/advisories/GHSA-cvx8-9ff6-54xq)
- The application must use the inline-detach (SOP) or MessageInspector code paths on untrusted input. (source: https://github.com/pgpainless/pgpainless/security/advisories/GHSA-cvx8-9ff6-54xq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-76088 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76088 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pgpainless/pgpainless/security/advisories/GHSA-cvx8-9ff6-54xq
- https://github.com/pgpainless/pgpainless/commit/7662f084595945f1000f3f2e1bc4e15302194dec
- https://github.com/pgpainless/pgpainless/commit/94572773f62e313ae905c48314de44efcf82420e
- https://github.com/pgpainless/pgpainless/releases/tag/1.7.8
- https://github.com/pgpainless/pgpainless/releases/tag/2.0.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76088
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76088"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • pgpainless pgpainless

    fixed in 1.7.8; From 2.0.0 · fixed in 2.0.4

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-76088

Is CVE-2026-76088 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Deeply nested compressed packets in untrusted input are followed without a bound. This can block threads, exhaust resources, and cause out-of-memory crashes in the consuming application, which is a denial of service.Source: github.com

Which versions are affected by CVE-2026-76088?

pgpainless: before 1.7.8; from 2.0.0 before 2.0.4.Source: cve.now feed data

Am I affected, and how do I check?

pgpainless-core 1.7.7 and earlier, and 2.0.0 through 2.0.3, are affected, but only where the application uses the inline-detach (SOP) wrapper interface or the MessageInspector modules on untrusted input. Check the pgpainless-core version in the build's dependency list and whether those modules are used.Source: github.com

How do I fix CVE-2026-76088?

Upgrade to 1.7.8 on the 1.x line or to 2.0.4 on the 2.0.x line.Source: github.com

More CVEs