Dynamics NAV 2017 · Version Status
Dynamics NAV 2017 End of Life Date
Dynamics NAV 2017 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.
⚡
Dynamics NAV 2017 reaches end of life on January 11, 2027. Plan your migration now — 93 days remaining.
📅 Get reminded before Dynamics NAV 2017 reaches EOL on January 11, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 11, 2027
93 days remaining
Latest Release
—
Standard release
Release Date
Oct 27, 2016
Dynamics NAV 2017 series
Lifecycle detail
Dynamics NAV 2017 was released on October 27, 2016 and support is scheduled to end on January 11, 2027 — a planned supported lifespan of 10 years and 3 months, in line with the 10 years and 1 month median for Dynamics NAV releases.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 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 →
Extended Support
Extended Dynamics NAV 2017 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Dynamics NAV Versions
| Version | Latest | EOL Date | Status |
|---|
| 2013 |
— |
Jan 10, 2023 |
EOL |
| 2013 R2 |
— |
Jan 10, 2023 |
EOL |
| 2015 |
— |
Jan 14, 2025 |
EOL |
| 2016 |
— |
Apr 14, 2026 |
EOL |
| → 2017 |
— |
Jan 11, 2027 |
Warning |
| 2018 |
— |
Jan 11, 2028 |
Active |
What does Dynamics NAV 2017 end of life mean?
When Dynamics NAV 2017 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 Dynamics NAV 2017 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Dynamics NAV 2018 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Dynamics NAV 2017 reach end of life?
Dynamics NAV 2017 reached end of life on January 11, 2027. That is 93 days remaining.
Is Dynamics NAV 2017 still supported?
Dynamics NAV 2017 is still supported but approaching end of life on January 11, 2027. Begin planning your migration now.
What should I upgrade to from Dynamics NAV 2017?
The recommended upgrade from Dynamics NAV 2017 is
Dynamics NAV 2018 — the latest actively supported version. Check the
Dynamics NAV full timeline for all supported versions.
What are the security risks of running Dynamics NAV 2017 past EOL?
When Dynamics NAV 2017 reaches end of life, the maintainers stop issuing 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 Dynamics NAV should migrate immediately or implement compensating controls.