dbcve.org
Hardened ImagesApplication · Redhat

CVE-2026-2625

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in rust-rpm-sequoia. An attacker can exploit this vulnerability by providing a specially crafted Red Hat Package Manager (RPM) file. During the RPM signature verification process, this crafted file can trigger an error in the OpenPGP signature parsing code, leading to an unconditional termination of the rpm process. This issue results in an application level denial of service, making the system unable to process RPM files for signature verification.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A flaw in rust-rpm-sequoia allows specially crafted RPM files to trigger an error in OpenPGP signature parsing code during verification, causing unconditional termination (crash) of the rpm process. This results in application-level denial of service where systems cannot process RPM files for signature verification.

MitigationUpdate rust-rpm-sequoia to a patched version that implements proper error handling in OpenPGP signature parsing to gracefully handle malformed signatures instead of crashing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hardened ImagesApplication
Affected:all versions
Rpm SequoiaApplication
Affected:all versions
Enterprise LinuxOperating system
Affected:= 9.0= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if rust-rpm-sequoia library is installed
    Run 'rpm -qa | grep -i sequoia' or 'dnf list installed | grep -i sequoia' to list installed packages containing 'sequoia' in their name
    Affected if Any package matching 'sequoia' related to RPM or OpenPGP is installed, as all versions of Sequoia Pgp Rpm Sequoia are affected
  2. Check the rpm package that provides RPM toolchain
    Run 'rpm -qa | grep -E "^rpm["" -""].*"' to identify the installed RPM package and its version. Also run 'rpm --version' to see which RPM implementation is in use
    Affected if The system uses the rust-rpm-sequoia implementation (check rpm --version output for 'sequoia' or library dependencies) as this library handles OpenPGP signature parsing
  3. Verify RHEL version if applicable
    Run 'cat /etc/os-release' or 'hostnamectl' to identify the Red Hat Enterprise Linux version
    Affected if Running RHEL 9.0 or RHEL 10.0 specifically, as these versions are listed as affected
  4. Confirm RPM database integrity tools are in use
    Run 'rpm -V rpm' or check 'rpm --eval %{_rpmversion}' to verify the RPM tools are active. Check 'ldd $(which rpm)' to see which libraries the rpm binary links against
    Affected if The rpm binary links against librpmio or related libraries that use the vulnerable sequoia component for signature verification
  5. Determine if system processes RPMs from external sources
    Review system logs (journalctl, /var/log/dnf.log) or cron jobs for automated RPM processing from repositories or external sources
    Affected if The system regularly installs or updates RPM packages from external repositories, enabling the attack vector

The environment is affected if it runs RHEL 9.0 or 10.0, uses Red Hat Hardened Images, or has any version of Sequoia Pgp Rpm Sequoia installed, and processes RPM files as this enables the DoS through malformed OpenPGP signature parsing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update rust-rpm-sequoia to a patched version that implements proper error handling in OpenPGP signature parsing to gracefully handle malformed signatures instead of crashing.

Fix this in Hardened Images Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2625 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data