Security readout for executives and security teams
Plain-English summary
A malicious .solv repository file can corrupt memory when processed by affected libsolv software. The documented impact is service or process failure, causing denial of service rather than data theft or modification. Exploitation requires a victim or system workflow to process the crafted file.
Executive priority
Treat as a scheduled, time-bound availability remediation, with faster action for exposed repository-processing infrastructure. The rating is moderate because impact may be severe operationally, but exploitation requires crafted input to be processed and no active exploitation is established.
Technical view
Negative size values in a crafted .solv file can cause repo_add_solv to calculate an undersized heap allocation, followed by an out-of-bounds write. This is classified as CWE-122. CVSS 3.1 is 6.5: network-reachable input, low complexity, no privileges, user interaction required, and high availability impact.
Likely exposure
Exposure includes the listed affected Red Hat Enterprise Linux, Hardened Images, OpenShift, Satellite, and RHUI products using libsolv-related packages. Risk is greatest where repository metadata or .solv files originate from untrusted or insufficiently controlled sources. The bundle provides exact package versions for only some products.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV. A successful attack requires delivery and processing of a specially crafted .solv file. Documented impact is denial of service; the supplied evidence does not claim confidentiality loss, integrity loss, or code execution.
Researcher notes
The vulnerable path is repo_add_solv: attacker-controlled negative sizes lead to an undersized allocation and heap out-of-bounds write. Product coverage is broad, but exact affected or fixed versions are incomplete in the bundle. Consult Red Hat's live advisories and the upstream pull request before making version-level determinations.
Mitigation direction
- Review Red Hat's CVE page and applicable RHSA advisories for supported fixes and product-specific instructions.
- Update affected libsolv, libsolv-main, rhcos, or Satellite Capsule components according to vendor guidance.
- Restrict repository metadata and .solv inputs to trusted, authenticated sources pending remediation.
- Prioritize systems whose automated workflows process externally supplied repository data.
Validation and detection
- Inventory the listed Red Hat products and identify installed libsolv-related package versions.
- Compare discovered packages with Red Hat's current CVE status and applicable RHSA advisories.
- Identify services and automation that ingest .solv files or repository metadata from external sources.
- After remediation, confirm vendor-supported package versions are installed and relevant services operate normally.
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-122: 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-9149 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:48818CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-9149CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2460380CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/openSUSE/libsolv/pull/617CVE 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.