NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

JLine vulnerable to out of memory errorGHSA-2268-98wh-qfhf

MEDIUMFix: jline/jline3@f3c60a3

GHSA-2268-98wh-qfhf is a medium-severity (CVSS 5.5) Out-of-bounds Write vulnerability in org.jline:jline-parent. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.jline:jline-parent — see the affected versions and patch details below.

Also known asCVE-2023-50572
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2268-98wh-qfhf.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk
0.00%0.25%0.50%0.76%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.jline:jline-parent

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

An issue in the component GroovyEngine.execute of JLine v3.24.1 allows attackers to cause an out of memory (OOM) error exception.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jline:jline-parentall versions3.25.0org.jline:jline-parent:3.25.0

Affected Products

1 product · 1 configurations
Application
jlinejline
< 3.25.0
range
Exploits & PoCs
1

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

An issue in the component GroovyEngine.execute of jline-groovy v3.24.1 a…

github.comNVDJan 2024

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update org.jline:jline-parent to 3.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2268-98wh-qfhf is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

An issue in the component `GroovyEngine.execute` of JLine v3.24.1 allows attackers to cause an out of memory (OOM) error exception.
O3 Security · Impact-Aware SCA

Is GHSA-2268-98wh-qfhf in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
JLine vulnerable to out of memory error (Medium 5.5)