Samsung Galaxy Watch End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Samsung Galaxy Watch versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| galaxy-watch | — | Aug 8, 2018 | No EOL date | Supported | Active |
| galaxy-watch-active | — | Mar 8, 2019 | No EOL date | Supported | Active |
| galaxy-watch-active2 | — | Sep 13, 2019 | No EOL date | Supported | Active |
| galaxy-watch3 | — | Aug 6, 2020 | No EOL date | Supported | Active |
| galaxy-watch4 | — | Aug 27, 2021 | TBD | Supported | Active |
| galaxy-watch4-classic | — | Aug 27, 2021 | TBD | Supported | Active |
| galaxy-watch5 | — | Aug 26, 2022 | TBD | Supported | Active |
| galaxy-watch5-pro | — | Aug 26, 2022 | TBD | Supported | Active |
| galaxy-watch6 | — | Aug 11, 2023 | TBD | Supported | Active |
| galaxy-watch6-classic | — | Aug 11, 2023 | TBD | Supported | Active |
| galaxy-watch-fe | — | Jun 24, 2024 | TBD | Supported | Active |
| galaxy-watch7 | — | Jul 24, 2024 | TBD | Supported | Active |
| galaxy-watch-ultra | — | Jul 24, 2024 | TBD | Supported | Active |
What does Samsung Galaxy Watch end of life mean for your organization?
When a version of Samsung Galaxy Watch 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 Samsung Galaxy Watch 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →