# CVE-2026-9150: Libsolv: stack-based buffer overflow in libsolv's debian metadata parser when handling sha384/sha512 checksums

> Attackers can cause denial of service via stack-based buffer overflow in libsolv's Debian metadata parser using crafted checksums.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-88053, CLSA-2026-1783588055, CLSA-2026-1783937718, DEBIAN-CVE-2026-9150, GHSA-p4w9-3pj8-mhq7, RHSA-2026:30649, UBUNTU-CVE-2026-9150

## What is CVE-2026-9150?

CVE-2026-9150 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in libsolv. This stack-based buffer overflow vulnerability occurs in libsolv's Debian metadata parser when processing specially crafted Debian repository metadata. An attacker could exploit this by providing malicious SHA384 or SHA512 checksum tags, leading to memory corruption and a denial of service (DoS) in the affected system.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsolv` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `libsolv-demo` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `libsolv-devel` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `libsolv-tools` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `libsolv-tools-base` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `perl-solv` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `python3-solv` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |
| `ruby-solv` | Red Hat:hummingbird:1 | All versions | 0:0.7.39-3.hum1 |

Products: Opensuse Libsolv, Redhat Enterprise Linux, Redhat Hardened Images, Redhat Openshift Container Platform, Redhat Satellite, Redhat Update Infrastructure.

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

Apply the vendor's patch.

## Is CVE-2026-9150 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2026-48864](https://insights.sbomify.com/CVE-2026-48864/): Libsolv: heap buffer overflow in libsolv repopagestore via unchecked decompression of malicious .solv page data (high 7.8)
- [CVE-2021-33928](https://insights.sbomify.com/CVE-2021-33928/): Memory corruption in n/a (high 7.5)
- [CVE-2021-33929](https://insights.sbomify.com/CVE-2021-33929/): Memory corruption in n/a (high 7.5)
- [CVE-2021-33930](https://insights.sbomify.com/CVE-2021-33930/): Memory corruption in n/a (high 7.5)
- [CVE-2021-33938](https://insights.sbomify.com/CVE-2021-33938/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9150 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9150 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-9150/ (Markdown: https://insights.sbomify.com/CVE-2026-9150/index.md)
```

## Sources

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

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