JSON-java (org.json) 20250517 · Version Status
JSON-java (org.json) 20250517 End of Life Date
JSON-java (org.json) 20250517 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) 20250517 is past end of life. This version no longer receives security patches. 309 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 24, 2025
309 days past EOL
Latest Release
20250517
Standard release
Release Date
May 17, 2025
JSON-java (org.json) 20250517 series
Where these dates come from
End of lifeDec 24, 2025Our catalog, built from the vendor pages · github.commedium · 1 source agrees ReleaseMay 17, 2025Our 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) 20250517 was released on May 17, 2025 and support ended on December 24, 2025 — a supported lifespan of 7 months, longer than the 4 months median for JSON-java (org.json) releases. Its latest release on record is 20250517, published May 17, 2025 — 7 months before support ended. It has been past its end-of-life date for 10 months. 3 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) 20250517 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) 20250517 end of life mean?
When JSON-java (org.json) 20250517 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) 20250517 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) 20250517 reach end of life?
JSON-java (org.json) 20250517 reached end of life on December 24, 2025. This version is no longer receiving security patches.
Is JSON-java (org.json) 20250517 still supported?
No. JSON-java (org.json) 20250517 reached end of life on December 24, 2025 and is no longer receiving security patches.
What should I upgrade to from JSON-java (org.json) 20250517?
The recommended upgrade from JSON-java (org.json) 20250517 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) 20250517 past EOL?
Since JSON-java (org.json) 20250517 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.