CVE-2010-2237

MEDIUMCVSS v2 · 4.44.4
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.4 — NVD rates that MEDIUM (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:L/AC:M/Au:S/C:C/I:N/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 0.3% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
4.4EG
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.3%CVSS v2: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Red Hat libvirt, possibly 0.6.1 through 0.8.2, looks up disk backing stores without referring to the user-defined main disk format, which might allow guest OS users to read arbitrary files on the host OS, and possibly have unspecified other impact, via unknown vectors.

CVSS v2.0 (legacy)
4.4MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.4MEDIUMlow confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
23rd
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 (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:L/AC:M/Au:S/C:C/I:N/A:N
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 19, 2010

Last Modified

April 29, 2026

References (9)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibvirt-bin (0.7.0-1ubuntu13.2) @ karmic2026-05-29ubuntu

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
libvirt—
  • every version up to 0.8.3-1: fixed in 0.8.3-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libvirt—
  • every version up to 0.8.3-1: fixed in 0.8.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libvirt—
  • every version up to 0.8.3-1: fixed in 0.8.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libvirt—
  • every version up to 0.8.3-1: fixed in 0.8.3-1
—

All Vendor Advisories

(1)

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 10× in last 7d / 26× 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 89 of 148 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-18 16:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-18 11:38 UTCEG score recompute
  3. 2026-10-17 16:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-16 16:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-15 16:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-14 16:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-13 16:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-12 21:41 UTCEG score recompute
  9. 2026-10-12 16:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-12 01:48 UTCEG score recompute
  11. 2026-10-11 13:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-09 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-08 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-07 23:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-06 15:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-05 17:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-04 23:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-03 14:20 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-01 18:10 UTCOSV refresh
  21. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-29 08:06 UTCEG score recompute
  23. 2026-09-27 13:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-09-26 15:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-09-24 13:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 64 more
  1. 2026-09-20 20:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-09-16 13:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-09-15 03:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-09-13 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-09-12 14:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-09-12 13:53 UTCOSV refresh
  7. 2026-09-10 09:24 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-09-06 13:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-09-05 15:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-09-04 13:55 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-08-28 21:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-08-26 14:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-08-25 13:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-08-24 19:03 UTCOSV refresh
  15. 2026-08-19 16:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-08-18 13:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-08-16 02:09 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-08-15 01:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-08-09 13:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-08-08 12:25 UTCOSV refresh
  21. 2026-08-07 16:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-08-06 13:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-08-05 19:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-08-04 15:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-08-01 04:10 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-07-26 13:41 UTCEG score recomputeFirst assessed: 4.4 MEDIUM
  28. 2026-07-25 14:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  29. 2026-07-23 14:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-07-23 05:19 UTCOSV refresh
  31. 2026-07-23 01:02 UTCEG score recompute
  32. 2026-07-23 00:38 UTCEG score recompute
  33. 2026-07-23 00:06 UTCEG score recompute
  34. 2026-07-22 21:45 UTCEG score recompute
  35. 2026-07-22 14:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-07-21 15:20 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-07-20 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-07-19 02:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-07-18 10:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-07-16 16:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-07-15 16:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  42. 2026-07-15 01:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-07-13 22:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-07-13 06:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-07-11 08:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-07-08 15:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-07-06 02:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-07-06 00:29 UTCOSV refresh
  49. 2026-07-05 02:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-07-02 14:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-07-01 15:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-06-30 23:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  53. 2026-06-29 14:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-06-28 14:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-06-28 04:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-06-27 03:05 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-06-25 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-06-24 14:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-06-23 21:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-06-22 14:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-06-21 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-06-21 01:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-06-19 19:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-06-18 17:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2010-2237?
CVE-2010-2237 is a medium-severity vulnerability; its CVE record was published on August 19, 2010. Red Hat libvirt, possibly 0.6.1 through 0.8.2, looks up disk backing stores without referring to the user-defined main disk format, which might allow guest OS users to read arbitrary files on the host OS, and possibly have unspecified other impact, via unknown vectors.
When was CVE-2010-2237 made public?
CVE-2010-2237 was made public on July 27, 2010: 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 19, 2010. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2010-2237 actively exploited?
CVE-2010-2237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2010-2237?
A fix for CVE-2010-2237 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2010-2237

Explore →

Is Your Infrastructure Affected by CVE-2010-2237?

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

Book a Demo →Browse All CVEs