AWS Lambda Node.js 24 · Version Status

AWS Lambda Node.js 24 End of Life Date

AWS Lambda Node.js 24 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

AWS Lambda Node.js 24 is actively supported. EOL date: July 1, 2028.
📅 Get reminded before AWS Lambda Node.js 24 reaches EOL on July 1, 2028 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Jul 1, 2028
691 days remaining
Latest Release
Standard release
Release Date
Nov 25, 2025
AWS Lambda Node.js 24 series
Lifecycle detail

AWS Lambda nodejs24.x was released on November 25, 2025 and support is scheduled to end on July 1, 2028 — a planned supported lifespan of 2 years and 7 months, shorter than the 3 years and 11 months median for AWS Lambda releases.

← AWS Lambda Python 3.14 All AWS Lambda versions AWS Lambda .NET 10 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 AWS Lambda Versions
VersionLatestEOL DateStatus
Node.js 0.10 Oct 31, 2016 EOL
Java 8 (AL1) Mar 3, 2027 Active
Python 2.7 May 30, 2022 EOL
Node.js 4.3 Mar 5, 2020 EOL
.NET Core 1.0 Jul 30, 2019 EOL
Node.js 6.10 Aug 12, 2019 EOL
Python 3.6 Aug 29, 2022 EOL
Node.js 4.3 edge Apr 30, 2020 EOL

What does AWS Lambda Node.js 24 end of life mean?

When AWS Lambda Node.js 24 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 AWS Lambda Node.js 24 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to AWS Lambda Java 17 (AL2023) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does AWS Lambda Node.js 24 reach end of life?
AWS Lambda Node.js 24 reached end of life on July 1, 2028. That is 691 days remaining.
Is AWS Lambda Node.js 24 still supported?
Yes, AWS Lambda Node.js 24 is currently supported. The EOL date is July 1, 2028.
What should I upgrade to from AWS Lambda Node.js 24?
The recommended upgrade from AWS Lambda Node.js 24 is AWS Lambda Java 17 (AL2023) — the latest actively supported version. Check the AWS Lambda full timeline for all supported versions.
What are the security risks of running AWS Lambda Node.js 24 past EOL?
When AWS Lambda Node.js 24 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 AWS Lambda should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →