Devuan 6 · Version Status
Devuan 6 End of Life Date
Devuan 6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Devuan 6 is actively supported. EOL date: June 30, 2030.
EOL Date
Jun 30, 2030
1513 days remaining
Latest Release
6.0.0
LTS release
Release Date
Nov 2, 2025
Devuan 6 series
| Version | Latest | EOL Date | Status |
|---|
| 1 LTS |
1.0.0 |
Jun 30, 2020 |
EOL |
| 2 LTS |
2.1 |
Jun 30, 2022 |
EOL |
| 3 LTS |
3.1.0 |
Jun 1, 2024 |
EOL |
| 4 LTS |
4.0.0 |
Aug 15, 2026 |
Warning |
| 5 LTS |
5.0.0 |
Jun 10, 2028 |
Active |
| → 6 LTS |
6.0.0 |
Jun 30, 2030 |
Active |
What does Devuan 6 end of life mean?
When Devuan 6 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 Devuan 6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Devuan 6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Devuan 6 reach end of life?
Devuan 6 reached end of life on June 30, 2030. That is 1513 days remaining.
Is Devuan 6 still supported?
Yes, Devuan 6 is currently supported. The EOL date is June 30, 2030.
What should I upgrade to from Devuan 6?
The recommended upgrade from Devuan 6 is
Devuan 6 — the latest actively supported version. Check the
Devuan full timeline for all supported versions.
What are the security risks of running Devuan 6 past EOL?
When Devuan 6 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 Devuan should migrate immediately or implement compensating controls.