Deno versions
Deno: update to 2.9.8. 2.8 and older have reached end of life in the lifecycle data.
Data: .
Which Deno branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 2.91 CVE record that this page reads | Fixes, no end date announced | 2.9.8 | 2.9.8 (this branch) |
| 2.85 CVE records that this page reads | Ended on 25 June 2026 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.76 CVE records that this page reads | Ended on 22 May 2026 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.62 CVE records that this page reads | Ended on 25 February 2026 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.54 CVE records that this page reads | Ended on 30 April 2026 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.4 | Ended on 10 September 2025 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.31 CVE record that this page reads | Ended on 1 July 2025 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.26 CVE records that this page reads | Ended on 31 October 2025 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.14 CVE records that this page reads | Ended on 30 April 2025 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 2.0 | Ended on 21 November 2024 | None, the branch has ended | 2.9.8 (move to 2.9) |
| 114 CVE records that this page reads | Ended on 9 October 2024 | None, the branch has ended | 2.9.8 (move to 2.9) |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 39 CVE records that the CVE Numbering Authorities GitHub_M and VulnCheck (as the CVE List names them) published and that name Deno. The fixes are from the 37 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.
2 records are not placed on a branch, so no branch or release row counts them: CVE-2023-33966 and CVE-2024-32468.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)