CVE-2005-2337: Ruby 1.6.x up to 1.6.8, 1.8.x up to 1.8.2, and 1.9.0 development up to 2005-09-01 allows attackers to bypass s

This month

HIGH 7.5DOWNGRADE

CVE-2005-2337 is a high-severity flaw (CVSS 7.5) affecting ruby. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Ruby 1.6.x up to 1.6.8, 1.8.x up to 1.8.2, and 1.9.0 development up to 2005-09-01 allows attackers to bypass safe level and taint flag protections and execute disallowed code when Ruby processes a program through standard input (stdin).

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	3.3% (top 12%)
CISA exploited list	No
Published	2005-10-07
Last modified	2026-06-16

Publisher (CNA): CERT/CC · Vendor: yukihiro matsumoto

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-10-07 23:02 UTCPublished CVE record published
2026-06-16 22:14 UTCUpdated Record last modified

yukihiro matsumoto ruby DOWNGRADE

Affected: 1.6 · 1.6.1 · 1.6.2 · 1.6.3 · 1.6.4 · 1.6.5 · 1.6.6 · 1.6.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.6

1. Check installed version

apt-cache policy ruby || rpm -q ruby || ruby --version

2. No fixed release: DOWNGRADE to a release before 1.6 (Debian / Ubuntu)

apt-cache madison ruby sudo apt install ruby=<VERSION_BEFORE_1.6> sudo apt-mark hold ruby

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ruby sudo dnf downgrade ruby-<VERSION_BEFORE_1.6> sudo dnf versionlock add ruby

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-2337?

ruby: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2337 being exploited?

CVE-2005-2337 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-2337 affect?

CVE-2005-2337 affects ruby. Severity is high (CVSS 7.5). Ruby 1.6.x up to 1.6.8, 1.8.x up to 1.8.2, and 1.9.0 development up to 2005-09-01 allows attackers to bypass safe level and taint flag protections and execute disallowed code when Ruby processes a program through standard input (stdin).

How urgent is CVE-2005-2337?

Priority 48/100. High severity

Software pages

Ruby vulnerabilities

Related CVEs

CVE-2026-97229 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
CVE-2026-46727 HIGH 8.1 UPGRADE An issue was discovered in Ruby 4 before 4.0.5
CVE-2023-28756 MEDIUM 5.3 UPGRADE DOWNGRADE A ReDoS issue was discovered in the Time component through 0.2.1 in Ruby through 3.2.1
CVE-2022-28739 HIGH 7.5 UPGRADE MITIGATE There is a buffer over-read in Ruby before 2.6.10, 2.7.x before 2.7.6, 3.x before 3.0.4, and 3.1.x before 3.1.
CVE-2022-28738 CRITICAL 9.8 UPGRADE A double free was found in the Regexp compiler in Ruby 3.x before 3.0.4 and 3.1.x before 3.1.2

References

← Back to latest CVEs