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.
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 | 1251 days past EOL | EOL |
| 20230227 | 20230227 | Feb 27, 2023 | Jun 18, 2023 | 1140 days past EOL | EOL |
| 20230618 | 20230618 | Jun 18, 2023 | Oct 13, 2023 | 1023 days past EOL | EOL |
| 20231013 | 20231013 | Oct 13, 2023 | Mar 3, 2024 | 881 days past EOL | EOL |
| 20240303 | 20240303 | Mar 3, 2024 | Dec 24, 2024 | 585 days past EOL | EOL |
| 20241224 | 20241224 | Dec 24, 2024 | Jan 7, 2025 | 571 days past EOL | EOL |
| 20250107 | 20250107 | Jan 7, 2025 | May 17, 2025 | 441 days past EOL | EOL |
| 20250517 | 20250517 | May 17, 2025 | Dec 24, 2025 | 220 days past EOL | EOL |
| 20251224 | 20251224 | Dec 24, 2025 | May 22, 2026 | 71 days past EOL | EOL |
| 20260522 | 20260522 | May 22, 2026 | Jul 19, 2026 | 13 days past EOL | EOL |
| 20260719 | 20260719 | Jul 19, 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.
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.
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 10 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for JSON-java (org.json) exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.