Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of org.jline:jline-reader from 3.0.0 before 3.30.15 and from 4.0.0 before 4.3.1 are affected. Where the HISTORY_IGNORE setting is supplied through user configuration or application settings, a crafted value containing regex metacharacters can cause catastrophic backtracking when a line is added to history, hanging the reader thread at high CPU. Upgrade to 3.30.15 or 4.3.1, or later. Avoid letting untrusted users set HISTORY_IGNORE.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.5 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0018, the 7th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:16 UTC First seen by agentprime
- 31 Oct 2026, 14:16 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5q95-hrpc-m3w3
- OSV: GHSA-5q95-hrpc-m3w3
- github.com/jline/jline3/security/advisories/GHSA-5q95-hrpc-m3w3
- github.com/jline/jline3/pull/2012
- github.com/jline/jline3/pull/2018
- github.com/jline/jline3/commit/1d5fc3099e77938b971e197211cad2d4fbb17541
- github.com/jline/jline3/commit/341ee69ccc57b7733c1b40d6993219b64b3206ae
- github.com/jline/jline3
- github.com/jline/jline3/releases/tag/4.3.1
- github.com/jline/jline3/releases/tag/jline-3.30.15