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
34%
KEV
Not listed

Published

May 20, 2026

Last Modified

September 1, 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

Vendor Advisories for CVE-2026-9150(6)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibsolv-0:0.7.29-8.el10_0.12026-07-31redhat
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libsolv0.7.17-1 ... 0.7.39-1 (25 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libsolv0.7.23-1 ... 0.7.39-1 (20 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libsolv0.7.32-1 ... 0.7.39-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libsolv0.7.32-1, 0.7.35-1, 0.7.36-10.7.37-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 80× 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 223 total refreshes for this CVE.

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

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 September 1, 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 65.9% 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

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

Start Free Scan →Browse All CVEs