CVE-2026-82327

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2026-08-28. A secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-67724 (ENISA EUVD) · GHSA-f53h-vhp4-v9wx (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in libsolv, a dependency-resolution library used by RPM-based package managers such as dnf and zypper to work with .solv repository cache files. When libsolv rewrites a .solv cache file, it reads directory-id values from the file's compressed filelist data without validating that they fall within the expected range. A corrupted or specially crafted .solv cache file (for example, one left in a torn state after an unclean system shutdown) can cause an out-of-bounds memory write when a tool such as dnf, yum, or zypper next processes it. Successful exploitation is expected to result in a crash of the affected tool (denial of service); it is not expected to allow arbitrary code execution because the out-of-bounds write always stores a fixed, non-attacker-controlled value.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

August 28, 2026

Last Modified

October 21, 2026

Advisory Details (2)

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

2525602 – (CVE-2026-82327) CVE-2026-82327 libsolv: libsolv: out-of-bounds write in repo_write() via unvalidated directory id from vertical/paged .solv filelist data

https://bugzilla.redhat.com/show_bug.cgi?id=2525602
Red HatMentions a patch (unverified)

CVE-2026-82327 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Affected Packages

(3 across 3 ecosystems)
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.

Data Freshness Timeline

(refreshed 20× in last 7d / 86× 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 188 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 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-82327?
CVE-2026-82327 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. A flaw was found in libsolv, a dependency-resolution library used by RPM-based package managers such as dnf and zypper to work with .solv repository cache files. When libsolv rewrites a .solv cache file, it reads directory-id values from the file's compressed filelist data without validating that…
When was CVE-2026-82327 made public?
CVE-2026-82327 was made public on August 28, 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 August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of October 21, 2026; the record at its source may have been updated since.
Is CVE-2026-82327 actively exploited?
CVE-2026-82327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82327?
CVE-2026-82327 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82327?
A fix for CVE-2026-82327 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82327 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-82327

Explore →

Is Your Infrastructure Affected by CVE-2026-82327?

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