CVE-2026-9149

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
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: Elevated riskExposed: 0

A fix is available — apply it.

A flaw was found in libsolv. This heap buffer overflow vulnerability occurs when a victim processes a specially crafted .solv file containing negative size values in the repo_add_solv function. This leads to an undersized memory allocation and a subsequent out-of-bounds write. An attacker could exploit this to cause a denial of service (DoS).

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

May 21, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: redhat, github_pr.
github_pr

Cope with integer overflow in data size arithmetics in repo_add_solv()

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

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

2460380 – (CVE-2026-9149) CVE-2026-9149 libsolv: Heap buffer overflow in libsolv repo_add_solv via negative maxsize from crafted .solv file

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

cve-details

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

Vendor Advisories for CVE-2026-9149(5)

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

Patch Availability(3)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× 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 232 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2026:21333

Frequently asked(5)

What is CVE-2026-9149?
CVE-2026-9149 is a medium vulnerability published on May 21, 2026. A flaw was found in libsolv. This heap buffer overflow vulnerability occurs when a victim processes a specially crafted .solv file containing negative size values in the repoaddsolv function. This leads to an undersized memory allocation and a subsequent out-of-bounds write. An attacker could…
When was CVE-2026-9149 disclosed?
CVE-2026-9149 was first published in the National Vulnerability Database on May 21, 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-9149 actively exploited?
CVE-2026-9149 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 75.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9149?
CVE-2026-9149 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-9149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9149, 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-9149

Explore →

Is Your Infrastructure Affected by CVE-2026-9149?

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

Start Free Scan →Browse All CVEs