Skip to main content

Sequoia OpenPGP CVE-2026-42784

| EUVDEUVD-2026-80888 HIGH
Improper Verification of Cryptographic Signature (CWE-347)
2026-09-16 secalert@redhat.com GHSA-g33h-rrj9-75qv
7.4
CVSS 3.1 · Vendor: redhat
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft certificate lacking key-flags subpacket
  2. Delivery
    Deliver certificate to victim application
  3. Exploit
    Library misinfers key flags
  4. Execution
    Back-signature check bypassed
  5. Persist
    Bind rogue subkey, forge signatures
  6. Impact
    Malicious signature accepted as valid

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Exploitation Conditions

Exploitation specifically requires an OpenPGP certificate that is missing a key-flags subpacket (the legacy/older-certificate code path); the library then incorrectly infers key flags, producing the key-flag confusion that bypasses the back-signature check and permits binding an arbitrary subkey. The victim system must actually process and verify the attacker-supplied certificate with sequoia-openpgp (UI:R), which is the main limiting factor - there is no default remote-service exposure. No authentication is required (PR:N). Any application relying on this library for OpenPGP signature verification is exposed once it ingests the crafted certificate.

Impact

This is a cryptographic signature-verification bypass (CWE-347) in the sequoia-openpgp library. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N, base 7.4) is internally coherent: no privileges required, low complexity, but user interaction is needed (a victim application/user must process the attacker-supplied certificate), and scope is changed because the library's flawed trust decision propagates to the relying application. Impact is integrity-only (I:H) - forged/illegitimately-bound signatures - with no confidentiality or availability impact, which matches the description. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so exploitation is: no public exploit identified at time of analysis. This is a genuine correctness/integrity flaw in a security-critical primitive (signature verification), so it is a real priority for any deployment that verifies OpenPGP certificates with this library, but the lack of active-exploitation or POC signals and the UI:R requirement mean it is not an urgent mass-exploitation threat. The 'Jwt Attack' tag is incorrect and misleading - this is OpenPGP, not JWT - and should not factor into triage.

Exploit ScenarioDerived

An attacker crafts a malicious OpenPGP certificate that lacks a key-flags subpacket (as older certificates do), causing sequoia-openpgp to infer key capabilities incorrectly and skip the back-signature check. The attacker binds an arbitrary subkey to their own certificate and presents it to a victim system that verifies signatures with the library, which then accepts forged signatures as valid. No public exploit code is identified at this time; exploitation requires the victim to process the attacker's certificate (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

Signature forgery in Sequoia OpenPGP (sequoia-openpgp) stems from incorrect key-flag inference for legacy OpenPGP certificates that lack a key-flags subpacket, letting an unauthenticated remote attacker bypass the back-signature check and bind an arbitrary subkey to their own certificate. This compromises cryptographic integrity for any application that uses the library to verify untrusted certificates, although exploitation requires the victim to process a crafted certificate (UI:R). No public exploit code or CISA KEV entry was identified in the provided data.

RemediationAI

No vendor-released patch was identified at time of analysis. Until a fix is available, applications should avoid verifying untrusted OpenPGP certificates with sequoia-openpgp; if that is not possible, add strict pre-validation that rejects any certificate lacking an explicit key-flags subpacket before processing, accepting that this may break interoperability with legitimate older certificates. Monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-42784 and the Bugzilla report at https://bugzilla.redhat.com/show_bug.cgi?id=2464122 for a patched version. A compensating control is to perform independent back-signature verification with a different OpenPGP implementation before trusting a subkey binding, though this adds complexity and potential performance overhead.

Affected ProductsAI

The affected product is the sequoia-openpgp library used to parse and verify OpenPGP certificates. No CPE strings or exact version ranges were supplied in the available intelligence; Red Hat tracks the issue at https://access.redhat.com/security/cve/CVE-2026-42784 and a bug report exists at https://bugzilla.redhat.com/show_bug.cgi?id=2464122. Applications that embed sequoia-openpgp for certificate validation, including those that process certificates missing a key-flags subpacket, are exposed.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OpenPGP certificates use key flags subpackets within self-signatures to declare capabilities such as certify, sign, encrypt, or authenticate, and a back-signature (subkey binding signature) cryptographically ties each subkey to the primary key. CVE-2026-42784 is a CWE-347 improper verification of cryptographic signature flaw in sequoia-openpgp: when an older certificate omits the key-flags subpacket, the library incorrectly infers key flags instead of safely rejecting or handling the absence. This inference discrepancy causes the back-signature check to be bypassed, so an attacker can illegitimately bind an arbitrary subkey to their own certificate and forge signatures. The root cause is in the certificate verification path that handles legacy certificates, and any application that relies on sequoia-openpgp for OpenPGP signature verification is exposed once it ingests such a crafted certificate.

Know when Rust gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (redhat) PRIMARY 7.4 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
vuln.today AI 7.4 HIGH

Certificate is network-delivered (AV:N) and unauthenticated (PR:N) but must be processed by the victim (UI:R); flawed verification propagates to the relying application (S:C) with integrity-only impact (I:H, C:N/A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
SUSE 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Red Hat 7.4 HIGH

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

A flaw was found in sequoia-openpgp. The library incorrectly infers key flags for older certificates when a key flags subpacket is missing, leading to a discrepancy in how key capabilities are viewed. This key flag confusion allows an attacker to bypass the back-signature check. Consequently, an attacker can illegitimately bind an arbitrary subkey to their own certificate and forge signatures, completely compromising cryptographic integrity.

Executive ViewAI

Why It Matters

A HIGH-severity signature-forgery flaw in the Sequoia OpenPGP library (sequoia-openpgp) lets a crafted certificate bypass the back-signature check and bind an attacker-controlled subkey to a legitimate certificate, undermining the cryptographic trust decisions made by any application that validates untrusted OpenPGP keys. Because Sequoia is a widely embedded library, exposure may extend well beyond teams that deploy it directly into third-party products and internal tooling. No vendor patch is available at this time, so leadership should treat this as an unmitigated integrity risk requiring immediate inventory and interim verification controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable or sandbox verification of untrusted OpenPGP certificates where business processes allow; enforce a strict allowlist of trusted keys and fingerprints rather than accepting arbitrary certificates; reject legacy OpenPGP certificates that lack a key-flags subpacket; add an independent back-signature/fingerprint validation step using a separate PGP implementation; and monitor the upstream Sequoia advisory channel for the eventual patched release and deploy it on an expedited timeline.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
Popular Rust OpenPGP library (sq, Debian tooling), but not universally deployed
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Rust

View all
CVE-2024-3566 CRITICAL POC
9.8 Apr 10

Command injection via Windows CreateProcess argument parsing affects multiple language runtimes and tooling (Node.js, PH

CVE-2021-31162 CRITICAL POC
9.8 Apr 14

In the standard library in Rust before 1.52.0, a double free can occur in the Vec::from_iter function if freeing the ele

CVE-2021-28879 CRITICAL POC
9.8 Apr 11

In the standard library in Rust before 1.52.0, the Zip implementation can report an incorrect size due to an integer ove

CVE-2026-58491 CRITICAL POC
9.3 Sep 21

Stored cross-site scripting and open redirect in Warpgate's SSO endpoints (versions prior to 0.25.5) allow an unauthenti

CVE-2021-29922 CRITICAL POC
9.1 Aug 07

library/std/src/net/parser.rs in Rust before 1.53.0 does not properly consider extraneous zero characters at the beginni

CVE-2026-77620 HIGH POC
8.7 Sep 22

Denial of service in the Vector observability pipeline's `logstash` source (versions 0.15.0 through 0.56.x) allows a rem

CVE-2019-12083 HIGH POC
8.1 May 13

The Rust Programming Language Standard Library 1.34.x before 1.34.2 contains a stabilized method which, if overridden, c

CVE-2026-96889 HIGH POC
7.8 Sep 23

Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity

CVE-2021-28878 HIGH POC
7.5 Apr 11

In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once fo

CVE-2021-28875 HIGH POC
7.5 Apr 11

In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe c

CVE-2019-16760 HIGH POC
7.5 Sep 30

Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration

CVE-2026-115905 CRITICAL
10.0 Oct 26

A parser differential in the Rust `zip` crate (zip2) through 9.0.4 lets a crafted archive present different filenames to

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Module for Development Tools 15 SP7 Not-Affected
SUSE Linux Enterprise Server 15 SP7 Not-Affected
SUSE Linux Enterprise Server 16.0 Not-Affected
SUSE Linux Enterprise Server 16.1 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy