Skip to content
Tuesday, October 13, 2026AboutContactRSS
Vulnerabilities

Microsoft Dynamics NAV 2017 Insecure Deserialization Flaw (CVE-2026-100214) Rated CVSS 8.8

A newly published high vulnerability in Microsoft Dynamics NAV 2017 carries a CVSS score of 8.8. Here is what is affected and how to respond.

Illustration: A dusty, obsolete server sits alone in a dim server room, its metal casing dented and worn.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-100214 affects Microsoft Dynamics NAV 2017.
  • CVSS 8.8 (High).
  • No exploitation confirmed yet.

A high insecure deserialization tracked as CVE-2026-100214 has been published in the National Vulnerability Database for Microsoft Dynamics NAV 2017, with a CVSS base score of 8.8.

At a glance

CVE
CVE-2026-100214
Product
Microsoft Dynamics NAV 2017
CVSS
8.8 High
Weakness
insecure deserialization
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: Deserialization of untrusted data in Dynamics Business Central allows an authorized attacker to execute code over a network.

Affected versions

VendorProductVersions
MicrosoftMicrosoft Dynamics NAV 2017before 30713
MicrosoftMicrosoft Dynamics NAV 2018before 11.0.50736.0

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C.

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

Background: Insecure deserialization

Look for base64-encoded parameters, unexpected object instantiation, or state changes that bypass authentication. Inspect input handling for unvalidated deserialization. Use allowlists for expected data types and verify integrity with digital signatures to prevent arbitrary code execution.

Read the full guide: Warning Signs of Insecure Deserialization in Web Applications

What to do and how to stay safe: CVE-2026-100214

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-100214?

CVE-2026-100214 is a insecure deserialization vulnerability in Microsoft Dynamics NAV 2017.

How severe is CVE-2026-100214?

It has a CVSS score of 8.8 High.

Is CVE-2026-100214 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-100214
  2. Reference
CVE-2026-100214Microsoft Dynamics NAV 2017High severity
Related articles