CVE-2026-2625: Rust-rpm-sequoia: rust-rpm-sequoia: denial of service via crafted rpm file during signature verification
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-2625 can crash the RPM signature verification process when it handles a specially crafted RPM file. The main business impact is disruption to package verification or update workflows, not data theft or privilege escalation. Red Hat rates it medium severity with CVSS 4.0.
Executive priority
Treat as a routine but timely Linux platform maintenance issue. Prioritize environments that ingest third-party RPMs or rely on automated package verification pipelines. This is not currently evidenced as exploited in the provided sources.
Technical view
The flaw is in rust-rpm-sequoia OpenPGP signature parsing during RPM signature verification. A crafted RPM can trigger an error path that unconditionally terminates the rpm process, causing application-level denial of service. Red Hat maps this to CWE-347 and lists affected rust-rpm-sequoia packages in RHEL 9, RHEL 10, and Red Hat Hardened Images.
Likely exposure
Exposure is most likely on Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat Hardened Images using the affected rust-rpm-sequoia packages to verify RPM signatures.
Exploitation context
Sources describe exploitation by providing a crafted RPM file for signature verification. CISA KEV is false in the provided data, and no cited source states active exploitation. Impact is limited to availability of the rpm verification process.
Researcher notes
Evidence supports denial of service during signature verification only. The source bundle does not provide exploit code, fixed package versions, or broader vendor impact beyond Red Hat-listed products. Avoid assuming compromise risk beyond process termination and availability loss.
Mitigation direction
Review Red Hat RHSA-2026:12682 for applicable updates and package guidance.
Prioritize systems that process untrusted or externally supplied RPM files.
Limit acceptance of RPM files to trusted sources where operationally possible.
Monitor Red Hat CVE and Bugzilla pages for updated remediation details.
Validation and detection
Inventory RHEL 9, RHEL 10, and Hardened Images in scope.
Check installed rust-rpm-sequoia or rust-rpm-sequoia-main package status.
Compare installed packages against Red Hat advisory applicability.
Review package verification failures or rpm process crashes in relevant logs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.