Security readout for executives and security teams
Plain-English summary
CVE-2026-48863 is a denial-of-service flaw in libsolv’s PGP signature verification. A malicious Ed25519 signature could crash automated package or repository processing. The business risk is interrupted software update or repository workflows, not disclosed data theft or integrity compromise based on the provided sources.
Executive priority
Treat as a high-priority availability risk for package-management infrastructure. Confirm exposure first, because the supplied Red Hat VEX marks listed Red Hat products unaffected and the bundle lacks a full affected-release matrix.
Technical view
The flaw is a stack-based buffer overflow caused by incorrect length handling when copying an EdDSA signature MPI into a stack buffer. The CVSS 3.1 score is 7.5, network exploitable with low complexity and availability-only impact. Red Hat’s listed products are marked unaffected in the supplied VEX data.
Likely exposure
Exposure is most relevant where libsolv processes PGP signatures from package or repository metadata. The provided Red Hat product list is marked unaffected. The bundle does not provide a complete affected version range or fixed release version beyond the referenced upstream commit.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. The described attack requires crafted signature content reaching libsolv’s PGP verification path, potentially through automated package or repository workflows.
Researcher notes
Evidence supports a stack overflow in EdDSA PGP signature verification with availability impact. The bundle references an upstream commit, Red Hat CVE entry, Bugzilla, and VEX, but does not provide proof of exploitation, full affected ranges, or a named fixed version.
Mitigation direction
- Check vendor advisories for affected and fixed libsolv package versions.
- Update libsolv from trusted vendor repositories when fixes are available.
- Limit automated repository processing to trusted, authenticated sources.
- Monitor update and repository services for crashes during signature verification.
- Use Red Hat VEX status to de-prioritize listed unaffected Red Hat products.
Validation and detection
- Inventory systems and containers containing libsolv.
- Identify automated package or repository workflows using libsolv verification.
- Compare installed products against vendor advisories and Red Hat VEX status.
- Review crash logs around package metadata or signature processing.
- Track the upstream libsolv commit and downstream package release notes.
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-48863 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
2 official scoresWe 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:N/S:U/C:N/I:N/A:H3.93.6redhatCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
- ADP timelineredhat-SADP
Reported to Red Hat.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- 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
- 2026-04-23T00:57:48.000Z: Reported to Red Hat.
- 2026-05-26T18:53:04.400Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2026-48863CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2460975CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/openSUSE/libsolv/commit/44f8c085045b1f771641091bbb2b810d12cff9e8#diff-309f245ec9b669ec78b8159c39e6f50130b4d4a0448f742685f7833d04bc4caaR592CVE reference, redhat
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48863.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
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.