Deno 2.2 · Version Status
Deno 2.2 End of Life Date
Deno 2.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Deno 2.2 is past end of life. This version no longer receives security patches. 190 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 31, 2025
190 days past EOL
Latest Release
2.2.15
LTS release
Release Date
Feb 18, 2025
Deno 2.2 series
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.46.3 |
Oct 9, 2024 |
EOL |
| 2.0 |
2.0.6 |
Nov 21, 2024 |
EOL |
| 2.1 LTS |
2.1.14 |
Apr 30, 2025 |
EOL |
| → 2.2 LTS |
2.2.15 |
Oct 31, 2025 |
EOL |
| 2.3 |
2.3.7 |
Jul 1, 2025 |
EOL |
| 2.4 |
2.4.5 |
Sep 10, 2025 |
EOL |
| 2.5 LTS |
2.5.7 |
Apr 30, 2026 |
EOL |
| 2.6 |
2.6.10 |
Feb 25, 2026 |
EOL |
What does Deno 2.2 end of life mean?
When Deno 2.2 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 Deno 2.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Deno 2.7 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Deno 2.2 reach end of life?
Deno 2.2 reached end of life on October 31, 2025. This version is no longer receiving security patches.
Is Deno 2.2 still supported?
No. Deno 2.2 reached end of life on October 31, 2025 and is no longer receiving security patches.
What should I upgrade to from Deno 2.2?
The recommended upgrade from Deno 2.2 is
Deno 2.7 — the latest actively supported version. Check the
Deno full timeline for all supported versions.
What are the security risks of running Deno 2.2 past EOL?
When Deno 2.2 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 Deno should migrate immediately or implement compensating controls.