Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliverySend crafted path-traversal request
-
ExploitEscape restricted directory boundary
-
ExecutionAccess or modify privileged resources
-
ImpactElevate privileges over network
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with at least low privileges on the target Dynamics Business Central instance (CVSS PR:L; description states 'authorized attacker'), so unauthenticated anonymous access is not sufficient. No user interaction is needed (UI:N) and the vector is network-reachable (AV:N) against a running instance. The core prerequisite is network access to the Business Central application endpoint plus valid credentials; the limiting factor is that the attacker must already be an authorized user, which confines the threat to insiders or holders of compromised/low-tier accounts rather than arbitrary remote attackers. No specific non-default feature toggle is named in the description beyond the path-handling code path itself. |
| Impact | CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates a network-exploitable, low-complexity flaw requiring only low-level authentication (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact - consistent with a privilege-escalation path-traversal (CWE-22) in Dynamics Business Central. No EPSS score was provided in the input, so exploitation probability cannot be quantified. KEV status is not present, so there is no confirmation of active exploitation, and no POC was supplied, so no public exploit identified at time of analysis. SSVC inputs (exploitation status, automatable, technical impact) were not provided and cannot be assessed. The signals therefore point to a genuinely serious vulnerability on paper (high CVSS, network vector, low barrier for an already-authenticated user) but with no evidence of real-world exploitation or public tooling, so this is a high-priority patching candidate rather than an emergency; the requirement for an existing authorized account (PR:L) meaningfully narrows the attacker population compared with an unauthenticated flaw. |
| Exploit ScenarioDerived | An attacker who already holds a low-privileged authenticated account on a Dynamics Business Central instance sends crafted requests over the network containing manipulated pathname input that escapes the intended restricted directory. By traversing to privileged files or resources, the attacker reads or modifies data outside their authorization boundary and elevates their privileges. No public exploit code or active exploitation is identified at time of analysis, and no user interaction is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Path traversal in Microsoft Dynamics Business Central (CWE-22) allows an authenticated user holding only low-level privileges to escape an intended directory boundary and elevate privileges over the network, carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity and availability impact and no user interaction required. Because the vector requires PR:L, anonymous remote attackers cannot exploit this alone - the realistic threat is insiders or holders of compromised low-privilege accounts who already possess valid credentials plus network reach to the Business Central application endpoint. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the sole supplied reference is Microsoft's MSRC update guide, which is the authoritative source for fix details.
RemediationAI
Apply the Microsoft fix identified in the MSRC update guide for CVE-2026-102226 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-102226); no exact fixed version number was supplied in the available data, so confirm the specific patched build/cumulative update for your deployment there - on-premises customers must install the corresponding Business Central cumulative update manually, while cloud service instances are patched by Microsoft and should simply be verified against the advisory. Until the patch is confirmed, reduce exposure with controls that specifically target the PR:L prerequisite: audit and remove unused or stale Business Central accounts and tighten permission sets so that few identities hold authenticated access, since the flaw requires a valid low-privileged session (this costs administrative effort and may disrupt legitimate non-admin workflows); restrict network reach to the Business Central application endpoint with firewall/segmentation rules or a reverse proxy so only trusted networks can reach it (this may break mobile or remote users and requires managing allowlists); and deploy reverse-proxy or WAF rules that reject requests containing traversal sequences in path or file parameters, while noting that encoding and separator variants can bypass naive signatures and that such rules risk false positives against legitimate file names. Log and alert on path values containing '../', encoded dot-segments, or absolute paths in requests to web service, upload, and report-retrieval endpoints, and monitor for low-privileged accounts touching files or operations outside their normal scope; these detections are a compensating measure only and do not replace patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-22, improper limitation of a pathname to a restricted directory: the application accepts user-influenced input that is used to construct a file or resource path without adequate canonicalization, normalization, or containment checks, so sequences such as ../ (and their encoded or alternate-separator variants) can resolve outside the directory the code intended to serve. In a Business Central context this class of bug is typically reachable through server-side components that resolve user-supplied paths - web service/API endpoints, file upload or download handlers, report and layout retrieval, or similar file-backed operations in the Business Central service tier - although the MSRC advisory does not name the specific code path. What distinguishes this instance is the impact profile: the assessed vector (S:U, C:H/I:H/A:H) indicates the traversal is used as a stepping stone to privilege escalation rather than mere file disclosure, so a low-privileged authenticated session can reach resources or operations normally reserved for higher-privileged users. The supplied data contains no CPE strings and no CWE mapping beyond CWE-22, and the advisory does not specify whether on-premises, cloud (SaaS), or both deployment models are affected; both inherit the same server-side path-handling logic and should be treated as in scope pending Microsoft's clarification.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable application endpoint (AV:N) with an authorized low-privilege account (PR:L) and no interaction (UI:N); path traversal yields full read/write access escalating to high C/I/A.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper limitation of a pathname to a restricted directory ('path traversal') in Dynamics Business Central allows an authorized attacker to elevate privileges over a network.
Executive ViewAI
CVE-2026-102226 is a high-severity path traversal flaw in Microsoft Dynamics Business Central that allows an authenticated user with only low-level privileges to break out of their intended directory boundary and operate with far greater rights across the application. Because Business Central typically holds financial ledgers, payroll, procurement and supply-chain records, a single compromised or malicious low-privilege account with network reach to the platform could read or alter core business data without any user interaction or advanced tooling. No public exploit code or confirmed active exploitation was identified at time of analysis, and no vendor-released patch is currently available, so the practical exposure today is insider and third-party accounts holding valid credentials rather than anonymous external attackers.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to Business Central endpoints to trusted internal segments and VPN, enforce MFA and conditional access on all accounts, aggressively reduce and recertify low-privilege role assignments, remove dormant and shared accounts, enable detailed audit logging with alerting for directory traversal patterns, and monitor the Microsoft MSRC update guide daily for the vendor fix.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-100375
GHSA-xjgf-2pjj-58vp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB