Gleam 1.3 · Version Status
Gleam 1.3 End of Life Date
Gleam 1.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Gleam 1.3 is past end of life. This version no longer receives security patches. 645 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 2, 2024
645 days past EOL
Latest Release
1.3.2
Standard release
Release Date
Jul 9, 2024
Gleam 1.3 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.0 |
Apr 16, 2024 |
EOL |
| 1.1 |
1.1.1 |
May 27, 2024 |
EOL |
| 1.2 |
1.2.1 |
Jul 9, 2024 |
EOL |
| → 1.3 |
1.3.2 |
Aug 2, 2024 |
EOL |
| 1.4 |
1.4.1 |
Sep 19, 2024 |
EOL |
| 1.5 |
1.5.1 |
Nov 18, 2024 |
EOL |
| 1.6 |
1.6.3 |
Jan 4, 2025 |
EOL |
| 1.7 |
1.7.0 |
Feb 7, 2025 |
EOL |
What does Gleam 1.3 end of life mean?
When Gleam 1.3 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 Gleam 1.3 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Gleam 1.15 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Gleam 1.3 reach end of life?
Gleam 1.3 reached end of life on August 2, 2024. This version is no longer receiving security patches.
Is Gleam 1.3 still supported?
No. Gleam 1.3 reached end of life on August 2, 2024 and is no longer receiving security patches.
What should I upgrade to from Gleam 1.3?
The recommended upgrade from Gleam 1.3 is
Gleam 1.15 — the latest actively supported version. Check the
Gleam full timeline for all supported versions.
What are the security risks of running Gleam 1.3 past EOL?
When Gleam 1.3 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 Gleam should migrate immediately or implement compensating controls.