CVE-2007-0469

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. 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 4.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.8%CVSS v2: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The extract_files function in installer.rb in RubyGems before 0.9.1 does not check whether files exist before overwriting them, which allows user-assisted remote attackers to overwrite arbitrary files, cause a denial of service, or execute arbitrary code via crafted GEM packages.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
48
EG Risk 48/100CISA SSVC

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
Severity93% × 45%
Exploitation5% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.8%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 24, 2007

Last Modified

April 23, 2026

References (12)

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
rubygems-update0.8.10 ... 0.9.0 (8 versions)
  • every version up to 0.9.1: fixed in 0.9.1
—

Data Freshness Timeline

(refreshed 5× in last 7d / 10× 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 115 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-2007-0469?
CVE-2007-0469 is a high vulnerability published on January 24, 2007. The extract_files function in installer.rb in RubyGems before 0.9.1 does not check whether files exist before overwriting them, which allows user-assisted remote attackers to overwrite arbitrary files, cause a denial of service, or execute arbitrary code via crafted GEM packages.
When was CVE-2007-0469 disclosed?
CVE-2007-0469 was first published on January 24, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-0469 actively exploited?
CVE-2007-0469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.8% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-0469?
A fix for CVE-2007-0469 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-2007-0469

Explore →

Is Your Infrastructure Affected by CVE-2007-0469?

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

Book a Demo →Browse All CVEs