Complete end-of-life dates, support windows, and security status for all Sony Xperia versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| l3 | — | Feb 1, 2019 | Dec 1, 2020 | 1985 days past EOL | EOL |
| 10 | — | Feb 27, 2019 | Oct 1, 2021 | 1681 days past EOL | EOL |
| 10-plus | — | Feb 27, 2019 | Oct 1, 2021 | 1681 days past EOL | EOL |
| 1 | — | May 30, 2019 | Oct 1, 2021 | 1681 days past EOL | EOL |
| 5 | — | Oct 5, 2019 | Oct 1, 2021 | 1681 days past EOL | EOL |
| l4 | — | Apr 28, 2020 | Jan 1, 2022 | 1589 days past EOL | EOL |
| 10-ii | — | May 5, 2020 | Mar 1, 2022 | 1530 days past EOL | EOL |
| 1-ii | — | May 22, 2020 | Jun 1, 2022 | 1438 days past EOL | EOL |
| 5-ii | — | Oct 12, 2020 | Oct 1, 2022 | 1316 days past EOL | EOL |
| pro | — | Jan 27, 2021 | Feb 1, 2023 | 1193 days past EOL | EOL |
| 10-iii | — | Jun 11, 2021 | Jul 1, 2023 | 1043 days past EOL | EOL |
| 1-iii | — | Aug 25, 2021 | Jul 1, 2023 | 1043 days past EOL | EOL |
| 5-iii | — | Oct 8, 2021 | Jul 1, 2023 | 1043 days past EOL | EOL |
| pro-i | — | Dec 2, 2021 | Nov 1, 2023 | 920 days past EOL | EOL |
| 1-iv | — | Jun 11, 2022 | May 1, 2025 | 373 days past EOL | EOL |
| 10-iv | — | Jun 30, 2022 | May 1, 2025 | 373 days past EOL | EOL |
| 5-iv | — | Sep 22, 2022 | Sep 1, 2025 | 250 days past EOL | EOL |
| 10-v | — | Jun 21, 2023 | Jun 1, 2026 | 23 days remaining | Warning |
| 1-v | — | Jul 28, 2023 | May 1, 2026 | 8 days past EOL | EOL |
| 5-v | — | Sep 25, 2023 | Aug 1, 2026 | 84 days remaining | Warning |
| 1-vi | — | Jun 3, 2024 | Apr 1, 2028 | 693 days remaining | Active |
| 10-vi | — | Jun 13, 2024 | May 1, 2028 | 723 days remaining | Active |
| 1-vii | — | Jun 4, 2025 | Apr 1, 2031 | 1788 days remaining | Active |
| 10-vii | — | Sep 19, 2025 | Aug 1, 2031 | 1910 days remaining | Active |
When a Sony Xperia version 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 Sony Xperia 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 →