---
title: "CWE-65: Windows Hard Link"
url: https://radicalnotion.ai/cwe/cwe-65
type: cwe
description: "The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-65: Windows Hard Link

- **Abstraction:** Variant
- **Structure:** Simple
- **Status:** Incomplete
- **CVEs with this as primary weakness:** 7
- **Of those, in CISA KEV:** 0
- **New in 2026:** 1
- **CWE catalog version:** 4.21

## Description

The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Implementation | - |
| Operation | - |

## Applicable platforms

**Operating systems:** Windows (Undetermined)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Confidentiality, Integrity | Read Files or Directories, Modify Files or Directories | Failure for a system to check for hard links can result in vulnerability to different types of attacks. For example, an attacker can escalate their privileges if a file used by a privileged program is replaced with a hard link to a sensitive file (e.g. AUTOEXEC.BAT). When the process opens the file, the attacker can assume the privileges of that process, or prevent the program from accurately processing data. |

## Potential mitigations

### Architecture and Design (Separation of Privilege)

Follow the principle of least privilege when assigning access rights to entities in a software system.

Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2002-0725 | Chain: File system allows local attackers to hide file usage activities via a hard link (CWE-65) to the target file, which causes the link to be recorded in the audit trail instead of the target file (CWE-221). |
| CVE-2003-0844 | Web server plugin allows local users to overwrite arbitrary files via a symlink attack on predictable temporary filenames. |

## Real CVEs with this weakness

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2020-6013 | Check Point ZoneAlarm Symlink Following Privilege Escalation Vulnerability | high | 8.8 | - | No | 2020-07-06 |
| CVE-2022-23742 | - | high | 7.8 | - | No | 2022-05-12 |
| CVE-2019-19231 | - | high | 7.8 | - | No | 2019-12-20 |
| CVE-2019-8452 | - | high | 7.8 | - | No | 2019-04-22 |
| CVE-2019-8455 | - | high | 7.1 | - | No | 2019-04-17 |
| CVE-2019-8454 | - | high | 7.0 | - | No | 2019-04-29 |
| CVE-2026-70019 | Windows Compressed Folder Information Disclosure Vulnerability | medium | 6.5 | - | No | 2026-09-08 |

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-59](https://radicalnotion.ai/cwe/cwe-59) | Improper Link Resolution Before File Access |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| PLOVER | Windows hard link | - | - |
| CERT C Secure Coding | Identify files using multiple file attributes | FIO05-C | - |
| Software Fault Patterns | Link in resource name resolution | SFP18 | - |

## Frequently asked questions

### What is CWE-65?

The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

### What CVEs are caused by CWE-65?

7 recorded CVEs are attributed to CWE-65, including CVE-2020-6013, CVE-2022-23742 and CVE-2019-19231.

### How do you prevent CWE-65?

Follow the principle of least privilege when assigning access rights to entities in a software system.

### What are the consequences of CWE-65?

Exploiting CWE-65 can lead to: Read Files or Directories, Modify Files or Directories.

### Is CWE-65 actively exploited?

7 recorded CVEs are caused by CWE-65; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/65.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-65). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
