How severe is CVE-2011-5036?

No CVSS score has been assigned to CVE-2011-5036 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-5036?

CVE-2011-5036 affects the following packages: org.jruby:jruby-parent (Maven), rack (RubyGems), rack (RubyGems), rack (RubyGems). Ecosystems affected: Maven, RubyGems.

How do I fix CVE-2011-5036?

Update org.jruby:jruby-parent to 1.6.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-5036 is resolved across your whole dependency graph.

How do I detect CVE-2011-5036 in my Maven, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2011-5036 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2011-5036?

O3 pinpoints whether CVE-2011-5036 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2011-5036 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2011-5036, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-5036?

CVE-2011-5036 has an EPSS (Exploit Prediction Scoring System) score of 4.0%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-5036?

CVE-2011-5036 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-5036 published, and has it been updated?

CVE-2011-5036 was published on December 30, 2011 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven💎 RubyGems

CVE-2011-5036

Rack Gem Subject to Denial of Service via Hash Collisions

Also known asGHSA-v6j3-7jrw-hq2p

Published

Dec 30, 2011

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

4.0%probability of exploitation in next 30 days

Lower Risk89th percentile+2.74%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

☕org.jruby:jruby-parent💎rack💎rack💎rack

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Rack before 1.1.3, 1.2.x before 1.2.5, and 1.3.x before 1.3.6 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jruby:jruby-parent`	all versions	1.6.5.1
💎RubyGems	`rack`	all versions	1.1.3
💎RubyGems	`rack`	≥ 1.2.0&&< 1.2.5	1.2.5
💎RubyGems	`rack`	≥ 1.3.0&&< 1.3.6	1.3.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Rack before 1.1.3, 1.2.x before 1.2.5, and 1.3.x before 1.3.6 computes h…

gist.github.comNVDOct 2013

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jruby:jruby-parent to 1.6.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-5036 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2011-5036 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2011-5036. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-5036 in your dependencies?

O3 detects CVE-2011-5036 across Maven, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works