CVE-2026-48864

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 26, 2026

Last Modified

October 14, 2026

Advisory Details (3)

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

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
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-48864
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:21333

Vendor Advisories for CVE-2026-48864(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcert-manager/cert-manager-istio-csr-rhel9:17913783952026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17914597112026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17917882872026-10-13redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17914597592026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17890290762026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17913710692026-10-13redhat
redhatrhai/base-image-rocm-rhel9:17907034942026-10-01redhat
redhatrhai/base-image-cuda-rhel9:17907035862026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907035062026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17907034972026-10-01redhat
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907035902026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035682026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17902768842026-09-30redhat
redhatrhai/base-image-cpu-rhel9:17902770452026-09-30redhat
redhatrhai/base-image-spyre-rhel9:17902768892026-09-30redhat
redhatrhai/base-image-cuda-rhel9:17902769742026-09-30redhat
redhatrhai/base-image-rocm-rhel9:17902768862026-09-30redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17902232792026-09-28redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17905899122026-09-28redhat
redhatcert-manager/cert-manager-trust-manager-rhel9:17905985932026-09-28redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17905899142026-09-28redhat
redhatcert-manager/cert-manager-operator-rhel9:17902724262026-09-28redhat
redhatcert-manager/cert-manager-operator-rhel9:17905898552026-09-28redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17902237192026-09-28redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202609080414-02026-09-17redhat
redhatopenshift/ose-rhel-coreos-9:417.94.202608250221-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202608241157-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202608180329-02026-08-31redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202608150307-02026-08-31redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libsolv0.7.17-1 ... 0.7.39-1 (25 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libsolv0.7.23-1 ... 0.7.40-1 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libsolv0.7.32-1 ... 0.7.40-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libsolv0.7.32-1 ... 0.7.40-1 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 93× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 479 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 379 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48864?
CVE-2026-48864 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-48864 was made public on May 26, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 26, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-48864 actively exploited?
CVE-2026-48864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48864?
CVE-2026-48864 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48864?
A fix for CVE-2026-48864 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48864 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs