JSON-java (org.json) 20260814 · Version Status
JSON-java (org.json) 20260814 End of Life Date
JSON-java (org.json) 20260814 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) 20260814 is actively supported. No end-of-life date has been announced yet.
Latest Release
20260814
Standard release
Release Date
Aug 14, 2026
JSON-java (org.json) 20260814 series
Where these dates come from
ReleaseAug 14, 2026Our 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) 20260814 was released on August 14, 2026 and has no published end-of-life date yet. Its most recent patch is 20260814, published August 14, 2026.
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
What does JSON-java (org.json) 20260814 end of life mean?
When JSON-java (org.json) 20260814 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) 20260814 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) 20260814 reach end of life?
JSON-java (org.json) 20260814 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is JSON-java (org.json) 20260814 still supported?
Yes, JSON-java (org.json) 20260814 is currently supported. The EOL date is TBD.
What should I upgrade to from JSON-java (org.json) 20260814?
The recommended upgrade from JSON-java (org.json) 20260814 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) 20260814 past EOL?
When JSON-java (org.json) 20260814 reaches end of life, the maintainers stop issuing 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.