# CVE-2026-48864: Libsolv: heap buffer overflow in libsolv repopagestore via unchecked decompression of malicious .solv page data

> Heap buffer overflow in libsolv allows attackers to execute code or cause denial of service via malicious .solv files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 14 Oct 2026
- **Also known as:** ALSA-2026:36730, ALSA-2026:39315, CLSA-2026-1783417594, CLSA-2026-1783524329, DEBIAN-CVE-2026-48864, GHSA-2927-mfhv-37vh, RHSA-2026:36730, RHSA-2026:39315, RHSA-2026:48811, RHSA-2026:48813, RHSA-2026:48814, RHSA-2026:48815, RHSA-2026:48816, RHSA-2026:48817, RHSA-2026:49775, RLSA-2026:36730, RLSA-2026:39315, UBUNTU-CVE-2026-48864

## What is CVE-2026-48864?

CVE-2026-48864 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 26 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in libsolv. This heap buffer overflow occurs during the decompression of attacker-controlled compressed data within `.solv` files due to insufficient input validation. An attacker can provide a specially crafted `.solv` file, which, when processed by a vulnerable application, can lead to out-of-bounds memory access. This could result in information disclosure, alteration of program execution, or a denial of service.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsolv` | AlmaLinux:8 | All versions | 0.7.20-7.el8_10 |
| `libsolv-devel` | AlmaLinux:8 | All versions | 0.7.20-7.el8_10 |
| `libsolv-tools` | AlmaLinux:8 | All versions | 0.7.20-7.el8_10 |
| `python3-solv` | AlmaLinux:8 | All versions | 0.7.20-7.el8_10 |
| `libsolv` | AlmaLinux:9 | All versions | 0.7.24-6.el9_8 |
| `libsolv-devel` | AlmaLinux:9 | All versions | 0.7.24-6.el9_8 |
| `libsolv-tools` | AlmaLinux:9 | All versions | 0.7.24-6.el9_8 |
| `python3-solv` | AlmaLinux:9 | All versions | 0.7.24-6.el9_8 |
| `libsolv` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-demo-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-tools-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `perl-solv-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `python3-solv` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `python3-solv-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `ruby-solv-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-demo-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-tools` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-tools-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `perl-solv-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `python3-solv-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `ruby-solv-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7.20-7.el8_10 |
| `libsolv-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-demo-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `perl-solv-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `python3-solv` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `python3-solv-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `ruby-solv-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.7.24-6.el9_8 |
| `libsolv` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-demo-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |
| `libsolv-tools-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |
| `perl-solv-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.7.24-6.el9_8 |

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

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

Apply the vendor's patch.

## Is CVE-2026-48864 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [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)
- [CVE-2026-9149](https://insights.sbomify.com/CVE-2026-9149/): Libsolv: heap buffer overflow in libsolv repo_add_solv via negative maxsize from crafted .solv file (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48864 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 26 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48864 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-48864/ (Markdown: https://insights.sbomify.com/CVE-2026-48864/index.md)
```

## Sources

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

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