CVE-2009-1904

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 8%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

The BigDecimal library in Ruby 1.8.6 before p369 and 1.8.7 before p173 allows context-dependent attackers to cause a denial of service (application crash) via a string argument that represents a large number, as demonstrated by an attempted conversion to the Float data type.

CVSS v3
—
EG Score
0.0(none)
EPSS
94.3%
KEV
Not listed

Published

June 11, 2009

Last Modified

April 23, 2026

References (62)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibruby1.9 (1.9.0.5-1ubuntu1.2) @ karmic2026-05-30ubuntu
ubuntulibruby1.9 (1.9.0.2-9ubuntu1.1) @ jaunty2026-05-30ubuntu
redhatruby-0:1.8.5-5.el5_3.72009-07-02redhat

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.

All Vendor Advisories

(3)

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 6× in last 7d / 39× 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.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCNZKoz/bigdecimal-segfault-fix
    First seen Jun 8, 2009

    Provides a quick workaround for the segfault bug in Ruby (CVE-2009-1904)

    Open source ↗

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2009-1904?
CVE-2009-1904 is a none vulnerability published on June 11, 2009. The BigDecimal library in Ruby 1.8.6 before p369 and 1.8.7 before p173 allows context-dependent attackers to cause a denial of service (application crash) via a string argument that represents a large number, as demonstrated by an attempted conversion to the Float data type.
When was CVE-2009-1904 disclosed?
CVE-2009-1904 was first published in the National Vulnerability Database on June 11, 2009, 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-2009-1904 actively exploited?
CVE-2009-1904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-1904?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-1904, 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

Explore the affected products and dependency analysis for CVE-2009-1904

Explore →

Is Your Infrastructure Affected by CVE-2009-1904?

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

Start Free Scan →Browse All CVEs