JSON-java (org.json) 20230618 · Version Status
JSON-java (org.json) 20230618 End of Life Date
JSON-java (org.json) 20230618 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (github.com); the source of each date is on the product page.
⚠
JSON-java (org.json) 20230618 is past end of life. This version no longer receives security patches. 1112 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 13, 2023
1112 days past EOL
Latest Release
20230618
Standard release
Release Date
Jun 18, 2023
JSON-java (org.json) 20230618 series
Where these dates come from
End of lifeOct 13, 2023Our catalog, built from the vendor pages · github.commedium · 1 source agrees ReleaseJun 18, 2023Our catalog, built from the vendor pages · github.commedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
JSON-java (org.json) 20230618 was released on June 18, 2023 and support ended on October 13, 2023 — a supported lifespan of 4 months, in line with the 4 months median for JSON-java (org.json) releases. Its latest release on record is 20230618, published June 18, 2023 — 4 months before support ended. It has been past its end-of-life date for 3 years and 1 month. 8 newer JSON-java (org.json) releases have shipped since.
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 →
Extended Support
Extended JSON-java (org.json) 20230618 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All JSON-java (org.json) Versions
What does JSON-java (org.json) 20230618 end of life mean?
When JSON-java (org.json) 20230618 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running JSON-java (org.json) 20230618 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to JSON-java (org.json) 20260814 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does JSON-java (org.json) 20230618 reach end of life?
JSON-java (org.json) 20230618 reached end of life on October 13, 2023. This version is no longer receiving security patches.
Is JSON-java (org.json) 20230618 still supported?
No. JSON-java (org.json) 20230618 reached end of life on October 13, 2023 and is no longer receiving security patches.
What should I upgrade to from JSON-java (org.json) 20230618?
The recommended upgrade from JSON-java (org.json) 20230618 is
JSON-java (org.json) 20260814 — 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) 20230618 past EOL?
Since JSON-java (org.json) 20230618 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL JSON-java (org.json) should migrate immediately or implement compensating controls.