EOL.WikiEOL.Wiki
← ← Back to all products

Mageia

Active
Operating SystemsLatest Version: 10Latest Release: N/A

Mageia is a community-driven Linux distribution forked from Mandriva Linux.

Support summary

Mageia 9 reaches EOL in 39 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Sep 29, 2026

Mageia 9 · 39 days left

Supported cycles

2

0 lts

Versions

10

Latest Version

10

Active Support

2

EOL

8

Lifecycle Timeline

Today
10
10
9
9
8
8
7
7
6
6
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
10Jun 29, 2026YesMar 31, 202810No
Active
9Aug 27, 2023YesSep 29, 20269No
Active
8Feb 26, 2021NoNov 30, 20238No
EOL
7Jul 1, 2019NoJun 30, 20217No
EOL
6Jul 16, 2017NoSep 30, 20196No
EOL
5Jun 20, 2015NoDec 31, 20175No
EOL
4Feb 1, 2014NoSep 19, 20154No
EOL
3May 19, 2013NoNov 26, 20143No
EOL
2May 22, 2012NoNov 22, 20132No
EOL
1Jun 1, 2011NoDec 1, 20121No
EOL

Data sources

Frequently Asked Questions

Which versions of Mageia have reached end of life?
The following Mageia versions have reached end of life and no longer receive security updates: 8, 7, 6, 5, 4, 3, 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Mageia 8?
Mageia 8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Mageia?
The latest version of Mageia is 10, released in the 10 release cycle.
How many versions of Mageia are currently supported?
Mageia currently has 2 actively supported version(s): 10, 9.
When does Mageia 10 reach end of life?
Mageia 10 is scheduled to reach end of life on Mar 31, 2028.
What should I do when Mageia reaches end of life?
When a Mageia version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.