How severe is GHSA-wmq2-jc9m-xp4m?

No CVSS score has been assigned to GHSA-wmq2-jc9m-xp4m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wmq2-jc9m-xp4m?

GHSA-wmq2-jc9m-xp4m affects the following packages: org.jruby:jruby-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-wmq2-jc9m-xp4m?

Update org.jruby:jruby-core to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmq2-jc9m-xp4m is resolved across your whole dependency graph.

How do I detect GHSA-wmq2-jc9m-xp4m in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-wmq2-jc9m-xp4m 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-wmq2-jc9m-xp4m?

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

Is GHSA-wmq2-jc9m-xp4m actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-wmq2-jc9m-xp4m, 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-wmq2-jc9m-xp4m?

GHSA-wmq2-jc9m-xp4m has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 82th 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-wmq2-jc9m-xp4m?

GHSA-wmq2-jc9m-xp4m is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-wmq2-jc9m-xp4m published, and has it been updated?

GHSA-wmq2-jc9m-xp4m was published on May 2, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-wmq2-jc9m-xp4m — jruby-core

GHSA-wmq2-jc9m-xp4m is a Cross-site Scripting (XSS) vulnerability in org.jruby:jruby-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.jruby:jruby-core — see the affected versions and patch details below.

Cross-site Scripting in in JRuby

Also known asCVE-2010-1330

Published

May 2, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% 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

1 pkg affected

☕org.jruby:jruby-core

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

Description

The regular expression engine in JRuby before 1.4.1, when $KCODE is set to 'u', does not properly handle characters immediately after a UTF-8 character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted string.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jruby:jruby-core`	all versions	1.4.1`org.jruby:jruby-core:1.4.1`

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.

The regular expression engine in JRuby before 1.4.1, when $KCODE is set …

jruby.orgNVDJan 2021

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jruby:jruby-core to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmq2-jc9m-xp4m 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-wmq2-jc9m-xp4m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wmq2-jc9m-xp4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

RHSA-2011:1456Red Hat JBoss SOA Platform 5.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wmq2-jc9m-xp4m in your dependencies?

O3 Security finds GHSA-wmq2-jc9m-xp4m across Maven 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