# CVE-2026-2625: Rust-rpm-sequoia: rust-rpm-sequoia: denial of service via crafted rpm file during signature verification

> An attacker can cause a denial of service by providing a crafted RPM file that crashes the signature verification process in rust-rpm-sequoia.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 2 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-2625, ECHO-2654-d857-4161, GHSA-p6j6-g4fc-g496, RHSA-2026:12682, UBUNTU-CVE-2026-2625

## What is CVE-2026-2625?

CVE-2026-2625 is a medium-severity denial of service vulnerability in Redhat Enterprise Linux, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-2625?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpm-sequoia` | Red Hat:hummingbird:1 | All versions | 0:1.10.1.1-1.2.hum1 |
| `rpm-sequoia-devel` | Red Hat:hummingbird:1 | All versions | 0:1.10.1.1-1.2.hum1 |
| `rust-rpm-sequoia` | Red Hat:hummingbird:1 | All versions | 0:1.10.1.1-1.2.hum1 |

Products: Redhat Enterprise Linux, Redhat Hardened Images, Sequoia-Pgp Rpm-Sequoia.

## How do I fix CVE-2026-2625?

Apply the vendor's patch.

## Is CVE-2026-2625 being exploited?

There is no known exploitation of CVE-2026-2625 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2625 and fix it if it is affected.

What it is: CVE-2026-2625 is a medium-severity denial of service vulnerability in Redhat Enterprise Linux, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2625 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2625/ (Markdown: https://insights.sbomify.com/CVE-2026-2625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2625
- OSV: https://osv.dev/vulnerability/CVE-2026-2625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2625/
Summaries are generated and may contain mistakes; the official description above is the record.