CWE · MITRE source
CWE-363Race Condition Enabling Link Following
The product checks the status of a file or directory before accessing it, which produces a race condition in which the file can be replaced with a link before the access is performed, causing the product to access the wrong file.
While developers might expect that there is a very narrow time window between the time of check and time of use, there is still a race condition. An attacker could cause the product to slow down (e.g. with memory consumption), causing the time window to become larger. Alternately, in some situations, the attacker could win the race by performing a large number of attacks.
Last updated: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-27102 | 2.0 | 9.9 | 0.0044 | 2024-03-13 |
CVE-2025-62161 | 2.0 | 10.0 | 0.0005 | 2025-11-06 |
CVE-2025-62596 | 2.0 | 10.0 | 0.0005 | 2025-11-06 |
CVE-2025-31133 | 1.6 | 7.8 | 0.0002 | 2025-11-06 |
CVE-2022-21658 | 1.5 | 7.3 | 0.0091 | 2022-01-20 |
CVE-2025-52565 | 1.5 | 7.5 | 0.0002 | 2025-11-06 |
CVE-2025-52881 | 1.5 | 7.5 | 0.0001 | 2025-11-06 |
CVE-2025-13492 | 1.4 | 7.0 | 0.0001 | 2025-12-03 |
CVE-2018-6693 | 1.1 | 5.3 | 0.0003 | 2018-09-18 |
CVE-2024-45310 | 0.7 | 3.6 | 0.0014 | 2024-09-03 |