JSON-java (org.json) 20260719 · Version Status

JSON-java (org.json) 20260719 End of Life Date

JSON-java (org.json) 20260719 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

JSON-java (org.json) 20260719 is actively supported. EOL date: TBD.
EOL Date
TBD
Supported
Latest Release
20260719
Standard release
Release Date
Jul 19, 2026
JSON-java (org.json) 20260719 series
Lifecycle detail

JSON-java (org.json) 20260719 was released on July 19, 2026 and has no published end-of-life date yet. Its most recent patch is 20260719, published July 19, 2026.

← JSON-java (org.json) 20260522 All JSON-java (org.json) versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All JSON-java (org.json) Versions
VersionLatestEOL DateStatus
20220320 20220320 Feb 27, 2023 EOL
20230227 20230227 Jun 18, 2023 EOL
20230618 20230618 Oct 13, 2023 EOL
20231013 20231013 Mar 3, 2024 EOL
20240303 20240303 Dec 24, 2024 EOL
20241224 20241224 Jan 7, 2025 EOL
20250107 20250107 May 17, 2025 EOL
20250517 20250517 Dec 24, 2025 EOL

What does JSON-java (org.json) 20260719 end of life mean?

When JSON-java (org.json) 20260719 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running JSON-java (org.json) 20260719 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to JSON-java (org.json) 20260719 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does JSON-java (org.json) 20260719 reach end of life?
JSON-java (org.json) 20260719 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is JSON-java (org.json) 20260719 still supported?
Yes, JSON-java (org.json) 20260719 is currently supported. The EOL date is TBD.
What should I upgrade to from JSON-java (org.json) 20260719?
The recommended upgrade from JSON-java (org.json) 20260719 is JSON-java (org.json) 20260719 — the latest actively supported version. Check the JSON-java (org.json) full timeline for all supported versions.
What are the security risks of running JSON-java (org.json) 20260719 past EOL?
When JSON-java (org.json) 20260719 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL JSON-java (org.json) should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →