CVE-2026-48864

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in libsolv. This heap buffer overflow occurs during the decompression of attacker-controlled compressed data within .solv files due to insufficient input validation. An attacker can provide a specially crafted .solv file, which, when processed by a vulnerable application, can lead to out-of-bounds memory access. This could result in information disclosure, alteration of program execution, or a denial of service.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
10.5%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated May 28, 2026
Patch available. Sources: redhat.
redhat

2460425 – (CVE-2026-48864) CVE-2026-48864 libsolv: Heap buffer overflow in libsolv repopagestore via unchecked decompression of malicious .solv page data

https://bugzilla.redhat.com/show_bug.cgi?id=2460425
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-48864

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibsolv-0:0.7.33-5.el10_22026-06-23redhat
redhatlibsolv-main-0.7.38-2.hum12026-05-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 197 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 12:42 UTCEG score recompute
  15. 2026-07-01 12:42 UTCVendor advisory
  16. 2026-07-01 12:42 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 14:57 UTCEG score recompute
  19. 2026-06-29 14:57 UTCVendor advisory
  20. 2026-06-29 14:57 UTCGHSA enrichment
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-28 23:23 UTCEG score recompute
  24. 2026-06-28 23:23 UTCVendor advisory
  25. 2026-06-28 23:23 UTCGHSA enrichment
Show 75 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 08:07 UTCEG score recompute
  3. 2026-06-28 08:07 UTCVendor advisory
  4. 2026-06-28 08:07 UTCGHSA enrichment
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 19:35 UTCEG score recompute
  8. 2026-06-27 19:35 UTCVendor advisory
  9. 2026-06-27 19:35 UTCGHSA enrichment
  10. 2026-06-27 07:06 UTCEG score recompute
  11. 2026-06-27 07:06 UTCVendor advisory
  12. 2026-06-27 07:06 UTCGHSA enrichment
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-26 17:54 UTCEG score recompute
  15. 2026-06-26 17:54 UTCVendor advisory
  16. 2026-06-26 17:54 UTCGHSA enrichment
  17. 2026-06-26 02:50 UTCEG score recompute
  18. 2026-06-26 02:50 UTCVendor advisory
  19. 2026-06-26 02:50 UTCGHSA enrichment
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 12:01 UTCEG score recompute
  22. 2026-06-25 12:01 UTCVendor advisory
  23. 2026-06-25 12:01 UTCGHSA enrichment
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
  26. 2026-06-23 21:33 UTCEPSS rescore
  27. 2026-06-22 14:25 UTCEPSS rescore
  28. 2026-06-22 14:25 UTCEPSS rescore
  29. 2026-06-21 14:56 UTCEPSS rescore
  30. 2026-06-21 14:56 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-21 01:59 UTCEPSS rescore
  33. 2026-06-19 19:26 UTCEPSS rescore
  34. 2026-06-19 19:26 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-17 19:19 UTCEG score recompute
  38. 2026-06-17 19:19 UTCVendor advisory
  39. 2026-06-17 19:19 UTCGHSA enrichment
  40. 2026-06-17 17:53 UTCEPSS rescore
  41. 2026-06-17 05:44 UTCEG score recompute
  42. 2026-06-17 05:44 UTCVendor advisory
  43. 2026-06-17 05:43 UTCGHSA enrichment
  44. 2026-06-16 17:53 UTCEPSS rescore
  45. 2026-06-16 17:15 UTCEG score recompute
  46. 2026-06-16 17:15 UTCVendor advisory
  47. 2026-06-16 17:15 UTCGHSA enrichment
  48. 2026-06-16 04:42 UTCEG score recompute
  49. 2026-06-16 04:42 UTCVendor advisory
  50. 2026-06-16 04:42 UTCGHSA enrichment
  51. 2026-06-15 17:49 UTCEPSS rescore
  52. 2026-06-15 17:49 UTCEPSS rescore
  53. 2026-06-15 15:58 UTCEG score recompute
  54. 2026-06-15 15:58 UTCVendor advisory
  55. 2026-06-15 15:58 UTCGHSA enrichment
  56. 2026-06-15 03:30 UTCEG score recompute
  57. 2026-06-15 03:30 UTCVendor advisory
  58. 2026-06-15 03:30 UTCGHSA enrichment
  59. 2026-06-14 23:18 UTCEPSS rescore
  60. 2026-06-14 15:02 UTCEG score recompute
  61. 2026-06-14 15:02 UTCVendor advisory
  62. 2026-06-14 15:02 UTCGHSA enrichment
  63. 2026-06-14 02:33 UTCEG score recompute
  64. 2026-06-14 02:33 UTCVendor advisory
  65. 2026-06-14 02:33 UTCGHSA enrichment
  66. 2026-06-13 23:00 UTCEPSS rescore
  67. 2026-06-13 14:04 UTCEG score recompute
  68. 2026-06-13 14:04 UTCVendor advisory
  69. 2026-06-13 14:04 UTCGHSA enrichment
  70. 2026-06-13 00:57 UTCEG score recompute
  71. 2026-06-13 00:57 UTCVendor advisory
  72. 2026-06-13 00:57 UTCGHSA enrichment
  73. 2026-06-12 23:12 UTCEPSS rescore
  74. 2026-06-12 23:12 UTCEPSS rescore
  75. 2026-06-12 12:28 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48864?
CVE-2026-48864 is a high vulnerability published on May 26, 2026. A flaw was found in libsolv. This heap buffer overflow occurs during the decompression of attacker-controlled compressed data within .solv files due to insufficient input validation. An attacker can provide a specially crafted .solv file, which, when processed by a vulnerable application, can lead…
When was CVE-2026-48864 disclosed?
CVE-2026-48864 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48864 actively exploited?
CVE-2026-48864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48864?
CVE-2026-48864 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-48864?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48864, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48864

Explore →

Is Your Infrastructure Affected by CVE-2026-48864?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.