Moment.js 2 · Version Status
Moment.js 2 End of Life Date
Moment.js 2 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (momentjs.com); the source of each date is on the product page.
✓
Moment.js 2 is actively supported. No end-of-life date has been announced yet.
Latest Release
2.31.0
Standard release
Release Date
Feb 8, 2013
Moment.js 2 series
Where these dates come from
End of active supportSep 15, 2020Our catalog, built from the vendor pages · momentjs.commedium · 1 source agrees ReleaseFeb 8, 2013Our catalog, built from the vendor pages · momentjs.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
Moment.js 2 was released on February 8, 2013 and has no published end-of-life date yet. Its most recent patch is 2.31.0, published September 15, 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 →
| Version | Latest | EOL Date | Status |
| → 2 |
2.31.0 |
EOL |
Active |
What does Moment.js 2 end of life mean?
When Moment.js 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: 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 Moment.js 2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Moment.js 2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Moment.js 2 reach end of life?
Moment.js 2 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Moment.js 2 still supported?
Yes, Moment.js 2 is currently supported. The EOL date is TBD.
What should I upgrade to from Moment.js 2?
The recommended upgrade from Moment.js 2 is
Moment.js 2 — the latest actively supported version. Check the
Moment.js full timeline for all supported versions.
What are the security risks of running Moment.js 2 past EOL?
When Moment.js 2 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 Moment.js should migrate immediately or implement compensating controls.