CVE-2026-9150: Libsolv: stack-based buffer overflow in libsolv's debian metadata parser when handling sha384/sha512 checksums
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.
Security readout for executives and security teams
Plain-English summary
Libsolv can crash when it processes deliberately malformed Debian repository metadata containing SHA384 or SHA512 checksum tags. Successful abuse could disrupt package-management or repository-related services, but the supplied evidence does not indicate data theft, data modification, or active exploitation.
Executive priority
Treat this as a prompt availability-focused remediation, especially for package infrastructure and systems using untrusted repositories. It is not supported as an emergency data-breach issue by the supplied evidence. Apply applicable vendor updates during the next accelerated maintenance window and investigate any unexplained package-manager crashes.
Technical view
CVE-2026-9150 is a CWE-121 stack-based buffer overflow in libsolv's Debian metadata parser. Network-delivered, crafted repository metadata can cause memory corruption after user interaction. CVSS 3.1 is 6.5, with availability impact rated high and confidentiality and integrity impacts rated none.
Likely exposure
Exposure is most likely where affected Red Hat systems process Debian repository metadata from untrusted or compromised sources. The bundle marks RHEL 7, 9, specified RHEL 10 releases, OpenShift 4, Satellite 6, RHUI 4, and listed Hardened Images affected. RHEL 8 is marked unaffected.
Exploitation context
The attack requires specially crafted repository metadata and user interaction, such as initiating metadata processing. No privileges are required and attack complexity is low. The bundle says KEV is false and provides no evidence of exploitation in the wild. Demonstrated impact is memory corruption and denial of service, not code execution.
Researcher notes
The documented primitive is a stack overflow involving SHA384 or SHA512 checksum tags. The CVSS vector requires user interaction and assigns no confidentiality or integrity impact. The sources supplied do not establish reliable code execution, public weaponization, affected upstream version ranges, or complete fixed-version details; consult the linked vendor errata and upstream change.
Mitigation direction
Review the applicable Red Hat errata and install vendor-provided corrected packages or images.
Prioritize systems that consume Debian metadata from external, third-party, or otherwise untrusted repositories.
Restrict repository configuration and metadata sources to trusted, authenticated infrastructure where operationally feasible.
If updates cannot be applied, consult Red Hat guidance for supported temporary mitigations.
Validation and detection
Inventory libsolv and libsolv-main package versions across the listed Red Hat products.
Compare installed packages and images with the applicable Red Hat errata.
Confirm RHEL 8 assets are correctly identified before treating them as unaffected.
Audit configured repositories and identify systems processing externally controlled Debian metadata.
After remediation, verify updated package deployment and normal package-management operation.
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-121: 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.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.