Filemaker End of Life Dates
other
Developers working with cross-platform relational databases often rely on a specific application to integrate a database engine with a graphical user interface and robust security features. FileMaker, developed by Claris International, a subsidiary of Apple, has been a go-to solution since its inception, providing users with the ability to visually modify databases. This application has been maintained by Claris International, which has ensured its relevance and functionality over the years, making it a popular choice among developers who require a user-friendly and secure database management system.
The end-of-life landscape for FileMaker reveals a significant number of versions that are no longer supported, with a total of 20 versions having reached their end-of-life, leaving only 2 active versions. The next version to expire is the 2024 version, which is set to reach its end-of-life on 2026-06-30, marking an important milestone for developers who are still utilizing this version. The most recent end-of-life date was 2025-12-31 for the 2023 version, underscoring the need for developers to stay up-to-date with the latest versions to ensure continuity and support.
Given the current security landscape, FileMaker has a remarkably clean track record, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the application does not have a known exploitation status. Despite this positive security picture, developers should remain vigilant and take proactive measures to ensure the security and integrity of their databases, such as regularly updating to the latest supported versions and following best practices for database management and security. By doing so, they can minimize potential risks and maintain the confidentiality, integrity, and availability of their data.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2026 | Jun 30, 2026 | — | Jun 30, 2028 | in 662d | — | — | Active | |
| 2025 | Jul 31, 2025 | — | Jul 31, 2027 | in 327d | — | — | Active | |
| 2024 | Jun 30, 2024 | — | Jun 30, 2026 | 69d ago | — | — | EOL | |
| 2023 | Apr 30, 2023 | — | Dec 31, 2025 | 250d ago | — | — | EOL | |
| 19.6 | Dec 31, 2022 | — | Dec 31, 2024 | 615d ago | — | — | EOL | |
| 19.5 | Jun 30, 2022 | — | Jun 30, 2024 | 799d ago | — | — | EOL | |
| 19.4 | Dec 1, 2021 | — | Dec 31, 2023 | 981d ago | — | — | EOL | |
| 19.3 | Jun 30, 2021 | — | Jul 31, 2023 | 1134d ago | — | — | EOL | |
| 19.2 | Mar 31, 2021 | — | Mar 31, 2023 | 1256d ago | — | — | EOL | |
| 19.1 | Sep 30, 2020 | — | Oct 31, 2022 | 1407d ago | — | — | EOL | |
| 19 | May 31, 2020 | — | May 31, 2022 | 1560d ago | — | — | EOL | |
| 18 | May 1, 2019 | — | Jun 25, 2021 | 1900d ago | — | — | EOL | |
| 17 | May 1, 2018 | — | Sep 18, 2020 | 2180d ago | — | — | EOL | |
| 16 | May 1, 2017 | — | Sep 18, 2020 | 2180d ago | — | — | EOL | |
| 15 | May 1, 2016 | — | Sep 20, 2019 | 2544d ago | — | — | EOL | |
| 14 | May 1, 2015 | — | Sep 21, 2018 | 2908d ago | — | — | EOL | |
| 13 | Dec 1, 2013 | — | Sep 22, 2017 | 3272d ago | — | — | EOL | |
| 12 | Apr 1, 2012 | — | Sep 23, 2016 | 3636d ago | — | — | EOL | |
| 11 | Mar 1, 2010 | — | Sep 25, 2015 | 4000d ago | — | — | EOL | |
| 10 | Jan 1, 2009 | — | Sep 27, 2014 | 4363d ago | — | — | EOL | |
| 9 | Jul 1, 2007 | — | Nov 15, 2011 | 5410d ago | — | — | EOL | |
| 8 | Aug 1, 2005 | — | Sep 23, 2010 | 5828d ago | — | — | EOL | |
| 7 | Mar 1, 2004 | — | Sep 26, 2008 | 6555d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
