JSON-java (org.json) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all JSON-java (org.json) versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
JSON-java (org.json) 20260814 is supported, with no end-of-life or end-of-support date announced yet. 11 of 12 tracked JSON-java (org.json) versions are past end of life; the most recent to reach it, 20260719, did so on August 14, 2026. The full JSON-java (org.json) 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 |
|---|---|---|---|---|---|
| 20220320 | 20220320 | Mar 20, 2022 | Feb 27, 2023 | 1295 days past EOL | EOL |
| 20230227 | 20230227 | Feb 27, 2023 | Jun 18, 2023 | 1184 days past EOL | EOL |
| 20230618 | 20230618 | Jun 18, 2023 | Oct 13, 2023 | 1067 days past EOL | EOL |
| 20231013 | 20231013 | Oct 13, 2023 | Mar 3, 2024 | 925 days past EOL | EOL |
| 20240303 | 20240303 | Mar 3, 2024 | Dec 24, 2024 | 629 days past EOL | EOL |
| 20241224 | 20241224 | Dec 24, 2024 | Jan 7, 2025 | 615 days past EOL | EOL |
| 20250107 | 20250107 | Jan 7, 2025 | May 17, 2025 | 485 days past EOL | EOL |
| 20250517 | 20250517 | May 17, 2025 | Dec 24, 2025 | 264 days past EOL | EOL |
| 20251224 | 20251224 | Dec 24, 2025 | May 22, 2026 | 115 days past EOL | EOL |
| 20260522 | 20260522 | May 22, 2026 | Jul 19, 2026 | 57 days past EOL | EOL |
| 20260719 | 20260719 | Jul 19, 2026 | Aug 14, 2026 | 31 days past EOL | EOL |
| 20260814 | 20260814 | Aug 14, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/json-java)
JSON-java (org.json) lifecycle status — the real story
JSON-java — org.json:json, the package every Java developer has typed at least once — has no support policy at all, and that is its lifecycle story. Versions are date stamps (20260719 is the release of July 19, 2026), there are no branches, no backports, and no LTS: each release simply supersedes the last, and the only version that ever receives a fix is the newest one. The moment a new date stamp appears on the releases page, every earlier version is end-of-life in the only sense that matters — it will never be patched. The table reflects that convention: each version's EOL date is the release date of its successor.
That convention has had real consequences. CVE-2022-45688, a stack-overflow flaw, was addressed in the 20230227 release; CVE-2023-5072, a denial-of-service issue, in 20231013 — and in both cases every earlier date stamp stayed vulnerable forever. Because org.json is pulled in transitively by thousands of libraries, the version in your dependency tree is usually whatever your framework pinned years ago, not the current release. A 2022 date stamp in a lockfile is not unusual; it is also carrying every org.json vulnerability disclosed since.
The upgrade path is usually trivial — the API is deliberately stable, and bumping the version is a one-line change. The hard part is knowing the old copy is there: date-stamped versions do not look outdated the way 1.x-versus-4.x does. Scan your dependency tree, and if a pinned transitive copy cannot move, commercial support for frozen org.json versions exists — see the support options below.
JSON-java (org.json) release and support pattern
Across the 12 release lines with a published release date, JSON-java (org.json) has shipped a new line roughly every 4 months (median interval). A line typically stays supported for about 4 months from its release to its end-of-life date (measured on the 11 lines with both dates published).
Of the 12 release lines tracked, 11 are past end of life and 1 is still within support. The newest line, 20260814, was released August 14, 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 JSON-java (org.json) end of life mean for your organization?
When a version of JSON-java (org.json) 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 JSON-java (org.json) 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 JSON-java (org.json) 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 JSON-java (org.json) versions. This is a bridge, not a permanent solution — plan your migration in parallel.
JSON-java (org.json) has 11 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for JSON-java (org.json) is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."