Security readout for executives and security teams
Plain-English summary
Libsolv can crash when it processes malicious Debian repository metadata containing specially crafted SHA384 or SHA512 checksum tags. An attacker must influence repository metadata and have it processed, so exposure depends heavily on repository trust. The documented impact is service disruption, not data theft or system takeover.
Executive priority
Treat this as a moderate, time-bounded patching priority. Accelerate remediation where repository metadata can originate outside a tightly controlled trust boundary or where package-management outages would disrupt production. Routine trusted-repository systems can follow the next suitable maintenance window after exposure validation.
Technical view
CVE-2026-9150 is a CWE-121 stack-based buffer overflow in libsolv’s Debian metadata parser. Network-delivered, crafted SHA384 or SHA512 tags can cause memory corruption after user interaction. CVSS 3.1 is 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), supporting high availability impact without documented confidentiality or integrity impact.
Likely exposure
Exposure is most likely where affected Red Hat systems process Debian metadata from compromised, malicious, or insufficiently trusted repositories. Listed affected products include several RHEL releases, OpenShift 4 components, Satellite 6, RHUI 4, and Hardened Images. RHEL 8 itself is listed as unaffected, although certain separate EL8-based product packages are affected.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires crafted repository metadata to reach the parser and be processed. Available evidence supports memory corruption and denial of service; it does not establish remote code execution.
Researcher notes
The evidence identifies SHA384 and SHA512 checksum-tag handling as the vulnerable path. The stated result is stack corruption causing denial of service. Exact upstream affected ranges, reliable exploitability beyond crashing, and code-execution impact are not established in the supplied material; consult the linked upstream change and vendor advisories for implementation-level confirmation.
Mitigation direction
- Review the applicable Red Hat advisory and install the vendor-provided corrected package for each affected product.
- Prioritize repository-management, update-infrastructure, OpenShift, and other systems that process externally influenced metadata.
- Until updated, avoid untrusted Debian repositories and limit metadata sources according to vendor guidance.
- Do not assume RHEL 8 status covers Satellite, RHUI, or OpenShift packages based on EL8.
Validation and detection
- Inventory installed libsolv, libsolv-main, and listed product-specific packages across relevant Red Hat environments.
- Compare product, release, and exact package build against Red Hat’s CVE page and applicable erratum.
- Review configured Debian metadata sources and identify repositories outside established trust boundaries.
- After remediation, rescan packages and confirm installed builds satisfy the applicable Red Hat advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-9150 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6redhatVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:21333CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:28236CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:30649CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:48818CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-9150CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2460379CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/openSUSE/libsolv/pull/616CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.