Answer in brief
CVE-2026-82327 records a Medium severity (CVSS 5.5) vulnerability in Libsolv: libsolv: out-of-bounds write in repo_write() via unvalidated directory id from vertical/paged .solv filelist data. The current sources do not mark it as known exploited. The current feed maps Red Hat/libsolv (generic), Red Hat/libsolv0 (generic), Red Hat/python3.12-solv (generic), Red Hat/python-solv (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/libsolv (generic), Red Hat/libsolv0 (generic), Red Hat/python3.12-solv (generic), Red Hat/python-solv (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/libsolvgeneric | * | Not reported |
| Red Hat/libsolv0generic | * | Not reported |
| Red Hat/python3.12-solvgeneric | * | Not reported |
| Red Hat/python-solvgeneric | * | Not reported |
| Red Hat/rhcosgeneric | * | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
A flaw was found in libsolv, a dependency-resolution library used by RPM-based package managers such as dnf and zypper to work with .solv repository cache files. When libsolv rewrites a .solv cache file, it reads directory-id values from the file's compressed filelist data without validating that they fall within the expected range. A corrupted or specially crafted .solv cache file (for example, one left in a torn state after an unclean system shutdown) can cause an out-of-bounds memory write when a tool such as dnf, yum, or zypper next processes it. Successful exploitation is expected to result in a crash of the affected tool (denial of service); it is not expected to allow arbitrary code execution because the out-of-bounds write always stores a fixed, non-attacker-controlled value.
Quoted source text, attributed separately from HOL analysis.