visionOS 1 · Version Status
visionOS 1 End of Life Date
visionOS 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
visionOS 1 is past end of life. This version no longer receives security patches. 782 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 16, 2024
782 days past EOL
Latest Release
1.3
Standard release
Release Date
Jan 31, 2024
visionOS 1 series
Where these dates come from
End of lifeSep 16, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJan 31, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
visionOS 1 was released on January 31, 2024 and support ended on September 16, 2024 — a supported lifespan of 8 months, shorter than the 1 year median for visionOS releases. Its latest release on record is 1.3, published July 29, 2024 — 2 months before support ended. It has been past its end-of-life date for 2 years and 2 months. 2 newer visionOS releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.3 |
Sep 16, 2024 |
EOL |
| 2 |
2.6 |
Sep 15, 2025 |
EOL |
| 26 |
26.6.1 |
Sep 14, 2026 |
EOL |
| 27 |
27.2 |
EOL |
Active |
What does visionOS 1 end of life mean?
When visionOS 1 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running visionOS 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to visionOS 27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does visionOS 1 reach end of life?
visionOS 1 reached end of life on September 16, 2024. This version is no longer receiving security patches.
Is visionOS 1 still supported?
No. visionOS 1 reached end of life on September 16, 2024 and is no longer receiving security patches.
What should I upgrade to from visionOS 1?
The recommended upgrade from visionOS 1 is
visionOS 27 — the latest actively supported version. Check the
visionOS full timeline for all supported versions.
What are the security risks of running visionOS 1 past EOL?
Since visionOS 1 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL visionOS should migrate immediately or implement compensating controls.