JsonPath (Jayway) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all JsonPath (Jayway) versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
JsonPath (Jayway) 3.0 is supported, with no end-of-life or end-of-support date announced yet. 6 of 7 tracked JsonPath (Jayway) versions are past end of life; the most recent to reach it, 2.10, did so on February 22, 2026. The full JsonPath (Jayway) lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.5 | 2.5.0 | Dec 10, 2020 | Jun 2, 2021 | 1935 days past EOL | EOL |
| 2.6 | 2.6.0 | Jun 2, 2021 | Jan 30, 2022 | 1693 days past EOL | EOL |
| 2.7 | 2.7.0 | Jan 30, 2022 | Mar 26, 2023 | 1273 days past EOL | EOL |
| 2.8 | 2.8.0 | Mar 26, 2023 | Jan 20, 2024 | 973 days past EOL | EOL |
| 2.9 | 2.9.0 | Jan 20, 2024 | Oct 31, 2025 | 323 days past EOL | EOL |
| 2.10 | 2.10.0 | Oct 31, 2025 | Feb 22, 2026 | 209 days past EOL | EOL |
| 3.0 | 3.0.0 | Feb 22, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/jsonpath)
JsonPath (Jayway) lifecycle status — the real story
JsonPath — com.jayway.jsonpath:json-path — is the library behind almost every $.store.book[0].title expression in Java code, and most projects that carry it never chose it: Spring's own MockMvc test assertions (jsonPath(…)) pull it in transitively, as do a long tail of API-testing and configuration tools. It has no published support policy and effectively a single line of development — each release supersedes the last, and only the newest version ever receives a fix. The table reflects that convention: each minor's EOL date is the release date of its successor.
The cadence makes the risk concrete. Releases are roughly annual — 2.8.0 in March 2023, 2.9.0 in January 2024, 2.10.0 in October 2025, and 3.0.0 in February 2026 — so a fix, when one comes, can trail a disclosure by months and strands every earlier version permanently. CVE-2023-51074, a stack-overflow flaw in Criteria.parse(), was disclosed against 2.8.0; only later releases carry the fix. Any dependency tree still resolving 2.9.x or older — common wherever a framework pinned the version years ago — is two or more generations behind the only line that receives fixes.
The upgrade is usually a version bump — the expression API is stable — but transitive pins are the trap: the copy in your build is whatever your framework chose, not the current release, and a two-year-old JsonPath does not look outdated the way a major-version gap does. Scan the dependency tree first. If a pinned line cannot move, commercial extended support for end-of-life JsonPath versions exists — see the support options below.
JsonPath (Jayway) release and support pattern
Across the 7 release lines with a published release date, JsonPath (Jayway) has shipped a new line roughly every 9 months (median interval). A line typically stays supported for about 9 months from its release to its end-of-life date (measured on the 6 lines with both dates published).
Of the 7 release lines tracked, 6 are past end of life and 1 is still within support. The newest line, 3.0, was released February 22, 2026. No end-of-life date is currently published for the 1 supported line.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does JsonPath (Jayway) end of life mean for your organization?
When a version of JsonPath (Jayway) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL JsonPath (Jayway) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when JsonPath (Jayway) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL JsonPath (Jayway) versions. This is a bridge, not a permanent solution — plan your migration in parallel.
JsonPath (Jayway) has 6 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for JsonPath (Jayway) exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans JsonPath (Jayway) 2.x. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."