A junction point is a Windows filesystem reparse point that makes one directory path resolve to another location. Attackers can abuse it when privileged processes follow user-controlled paths without validation, redirecting file operations into sensitive directories or unintended targets.
What a junction point does
A junction point is a Windows reparse point that redirects one directory path to another location. It behaves like a normal folder entry to many processes, which is useful for compatibility and redirection, but it also means path handling must be trusted only after validation, not by appearance alone.
Why junction points are security-sensitive
Junction points matter because security decisions often hinge on where a privileged process thinks it is writing or reading. If code follows a user-influenced path without checking the final target, an attacker can steer file operations into a protected directory, replace expected inputs, or influence updates, logs, or configuration files in unintended places.
That risk is strongest when the process runs with elevated rights, performs file operations on behalf of less privileged users, or assumes directory names are stable. The danger is not the junction itself, but the trust placed in a path before resolving where it really points.
How junction point abuse works
Abuse usually depends on path confusion. A program may validate the visible directory name, then later open the resolved target and unknowingly cross a trust boundary. On Windows, this can let an attacker redirect actions into sensitive locations if the software does not inspect reparse behavior, canonicalise paths correctly, or restrict which directories may be traversed.
Junction abuse is especially relevant in workflows that recurse through directories, install software, clean temporary locations, or process archives and extracted content. In those cases, a path that appears safe during review can become dangerous once the reparse point is followed.
Defensive controls for Windows path redirection
Defence starts with treating file paths as security-relevant input. Sensitive code should resolve the actual target before acting, enforce allowlists for trusted locations, and avoid performing privileged writes in directories that untrusted users can influence. When possible, use APIs and checks that expose reparse points rather than silently traversing them.
Operationally, organisations should watch for unexpected filesystem links in writable locations, review installer and cleanup logic, and harden any service that handles user-supplied paths. If a process must operate on such paths, it should fail closed when the resolved target falls outside the intended directory boundary.
Risk and Threat Considerations
Junction points create a classic path traversal and privilege-confusion risk when a trusted process follows a path that an attacker can influence. The result can be unintended writes, file replacement, or escalation from an untrusted location into a sensitive one.
Failure mechanism: The application validates the apparent folder path, then follows a junction to a different destination after the check has already passed.
Impact: An attacker may redirect privileged file operations into protected directories, overwrite security-critical files, or tamper with data that a service later trusts.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1070 — Indicator Removal on Host | Junction abuse can hide or redirect file activity during host tampering. |
| Recommendation — Map suspicious junction use to host tampering techniques and investigate redirected file operations. | ||
| NIST SP 800-53 Rev 5 | SI-7 — Software, Firmware, and Information Integrity | Integrity controls apply when a junction can redirect privileged file writes or reads. |
| Recommendation — Validate file targets before privileged operations and block unexpected path redirection. | ||
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Secure configuration helps prevent unsafe filesystem handling in privileged workflows. |
| Recommendation — Harden file-handling services so they do not trust user-controlled paths or reparse targets. | ||
Practitioner Guidance
What to watch for: Review any code path that accepts directory input, recurses through folders, or performs privileged file operations in locations a user can influence. Those are the places where junction handling mistakes become exploitable.
Governance implication: Treat junction-aware path handling as part of secure coding and platform hardening standards, especially for installers, updaters, backup tools, and administrative utilities. The key decision is not whether junctions are allowed, but whether the software verifies the resolved target before acting.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org