webpack End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all webpack versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3 | 3.12.0 | Jun 19, 2017 | Feb 25, 2018 | 3055 days past EOL | EOL |
| 4 | 4.47.0 | Feb 25, 2018 | Oct 10, 2020 | 2097 days past EOL | EOL |
| 5 | 5.108.4 | Oct 10, 2020 | TBD | Supported | Active |
webpack lifecycle status — the real story
webpack 5 is the only actively supported line — the project's security policy covers the latest release line, and 5.x has been maintained continuously since October 2020 with releases as recent as July 2026. webpack 4 is effectively end-of-life: its final release (4.47.0) shipped in September 2023, and the plugin/loader ecosystem has moved to 5-only APIs, so staying on 4 increasingly means pinning old versions of everything around it.
The 4-to-5 migration is a known, documented project (Node version bumps, polyfill removal for Node core modules, asset-module changes). Teams that defer it accumulate a compounding cost because each dependency's webpack-4-compatible version also stops receiving security fixes.
webpack 3 and earlier have been unsupported since 2018 and belong in any legacy-risk register on sight.
What does webpack end of life mean for your organization?
When a version of webpack reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL webpack should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL webpack versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →