cve.bz

CVE-2006-4111 rubyonrails: Code Injection

no score yetEPSS 2.3%Fix available

rubyonrails: no CVSS score yet. EPSS 2.3% estimated probability of exploitation activity in the next 30 days. Fixed in rails 1.1.6.

On this page
Ruby on Rails before 1.1.5 allows remote attackers to execute Ruby code with "severe" or "serious" impact via a File Upload request with an HTTP header that modifies the LOAD_PATH variable, a different vulnerability than CVE-2006-4112.
EPSS
2.3% (unchanged from 2.3% a week ago; 2.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2006-4111 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-4111?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-4111?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-4111 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
rubyonrails:rails0.9.1
rubyonrails:rails0.9.2
rubyonrails:rails0.9.3
rubyonrails:rails0.9.4
rubyonrails:rails0.9.4.1
rubyonrails:rails0.10.0
rubyonrails:rails0.10.1
rubyonrails:rails0.11.0
rubyonrails:rails0.11.1
rubyonrails:rails0.12.0
rubyonrails:rails0.12.1
rubyonrails:rails0.13.0
rubyonrails:rails0.13.1
rubyonrails:rails0.14.1
rubyonrails:rails0.14.2
rubyonrails:rails0.14.3
rubyonrails:rails0.14.4
rubyonrails:rails1.0.0
rubyonrails:rails1.1.0
rubyonrails:rails1.1.1
rubyonrails:rails1.1.2
rubyonrails:rails1.1.3
rubyonrails:ruby_on_railsthrough 1.1.4
rubyonrails:ruby_on_rails0.5.0
rubyonrails:ruby_on_rails0.5.5
rubyonrails:ruby_on_rails0.5.6
rubyonrails:ruby_on_rails0.5.7
rubyonrails:ruby_on_rails0.6.0
rubyonrails:ruby_on_rails0.6.5
rubyonrails:ruby_on_rails0.7.0
rubyonrails:ruby_on_rails0.8.0
rubyonrails:ruby_on_rails0.8.5
rubyonrails:ruby_on_rails0.9.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rvpq-5xqx-pfppRubyGemsrails>=1.1.0 <1.1.61.1.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14rails1.1.5-1DEBIAN-CVE-2006-4111

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON