Pixel Watch 4 · Version Status
Pixel Watch 4 End of Life Date
Pixel Watch 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Pixel Watch 4 is actively supported. EOL date: October 1, 2028.
EOL Date
Oct 1, 2028
876 days remaining
Latest Release
—
Standard release
Release Date
Oct 9, 2025
Pixel Watch 4 series
| Version | Latest | EOL Date | Status |
|---|
| 1 |
— |
Oct 1, 2025 |
EOL |
| 2 |
— |
Oct 1, 2026 |
Warning |
| 3 |
— |
Oct 1, 2027 |
Active |
| → 4 |
— |
Oct 1, 2028 |
Active |
What does Pixel Watch 4 end of life mean?
When Pixel Watch 4 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 Pixel Watch 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Pixel Watch 4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Pixel Watch 4 reach end of life?
Pixel Watch 4 reached end of life on October 1, 2028. That is 876 days remaining.
Is Pixel Watch 4 still supported?
Yes, Pixel Watch 4 is currently supported. The EOL date is October 1, 2028.
What should I upgrade to from Pixel Watch 4?
The recommended upgrade from Pixel Watch 4 is
Pixel Watch 4 — the latest actively supported version. Check the
Pixel Watch full timeline for all supported versions.
What are the security risks of running Pixel Watch 4 past EOL?
When Pixel Watch 4 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 Pixel Watch should migrate immediately or implement compensating controls.