CVE-2026-9150

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-05-21. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libsolv. This stack-based buffer overflow vulnerability occurs in libsolv's Debian metadata parser when processing specially crafted Debian repository metadata. An attacker could exploit this by providing malicious SHA384 or SHA512 checksum tags, leading to memory corruption and a denial of service (DoS) in the affected system.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (3)

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

Fix a buffer overflow when copying SHA-384/512 checksum from a Debian repository

Fix merged in openSUSE/libsolv PR #616 on 2026-04-22 — awaiting tagged release

https://github.com/openSUSE/libsolv/pull/616
redhat

2460379 – (CVE-2026-9150) CVE-2026-9150 libsolv: Stack-based buffer overflow in libsolv's Debian metadata parser when handling SHA384/SHA512 checksums

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

cve-details

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibsolv-main-0.7.39-3.hum12026-06-28redhat
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 12× in last 7d / 40× 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 111 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9150?
CVE-2026-9150 is a medium vulnerability published on May 20, 2026. A flaw was found in libsolv. This stack-based buffer overflow vulnerability occurs in libsolv's Debian metadata parser when processing specially crafted Debian repository metadata. An attacker could exploit this by providing malicious SHA384 or SHA512 checksum tags, leading to memory corruption and…
When was CVE-2026-9150 disclosed?
CVE-2026-9150 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9150 actively exploited?
CVE-2026-9150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.4% of all scored CVEs.
What is the CVSS score of CVE-2026-9150?
CVE-2026-9150 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-9150?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9150, 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-9150

Explore →

Is Your Infrastructure Affected by CVE-2026-9150?

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