How severe is GHSA-v6j3-7jrw-hq2p?

No CVSS score has been assigned to GHSA-v6j3-7jrw-hq2p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v6j3-7jrw-hq2p?

GHSA-v6j3-7jrw-hq2p affects the following packages: org.jruby:jruby-parent (Maven), rack (RubyGems), rack (RubyGems), rack (RubyGems). Ecosystems affected: Maven, RubyGems.

How do I fix GHSA-v6j3-7jrw-hq2p?

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 GHSA-v6j3-7jrw-hq2p is resolved across your whole dependency graph.

How do I detect GHSA-v6j3-7jrw-hq2p 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v6j3-7jrw-hq2p 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 GHSA-v6j3-7jrw-hq2p?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v6j3-7jrw-hq2p can be triaged on real exposure rather than presence alone.

Is GHSA-v6j3-7jrw-hq2p actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-v6j3-7jrw-hq2p, 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 GHSA-v6j3-7jrw-hq2p?

GHSA-v6j3-7jrw-hq2p has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th 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 GHSA-v6j3-7jrw-hq2p?

GHSA-v6j3-7jrw-hq2p 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 GHSA-v6j3-7jrw-hq2p published, and has it been updated?

GHSA-v6j3-7jrw-hq2p was published on May 17, 2022 and was last updated on November 30, 2024. 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

Not in CISA KEV

GHSA-v6j3-7jrw-hq2p — jruby-parent

GHSA-v6j3-7jrw-hq2p is a CWE-310 vulnerability in org.jruby:jruby-parent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.jruby:jruby-parent — see the affected versions and patch details below.

Rack Gem Subject to Denial of Service via Hash Collisions

Also known asCVE-2011-5036

Published

May 17, 2022

Updated

Nov 30, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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.

Real-World Exposure

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`org.jruby:jruby-parent:1.6.5.1`
💎RubyGems	`rack`	all versions	1.1.3`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 1.2.0&&< 1.2.5	1.2.5`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 1.3.0&&< 1.3.6	1.3.6`bundle update rack --conservative`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 GHSA-v6j3-7jrw-hq2p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v6j3-7jrw-hq2p can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v6j3-7jrw-hq2p. 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 GHSA-v6j3-7jrw-hq2p in your dependencies?

O3 Security finds GHSA-v6j3-7jrw-hq2p across Maven, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works