# CVE-2024-8244: Walk/WalkDir in path/filepath susceptible to symlink race

> Attackers can exploit a race condition in Go's filepath.Walk to bypass symlink restrictions, potentially accessing unintended files.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-8244, ECHO-cf03-9570-1659, GHSA-v9vr-w93g-qph7, UBUNTU-CVE-2024-8244

## What is CVE-2024-8244?

CVE-2024-8244 is a low-severity vulnerability in Go standard library path/filepath, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.

## Which versions are affected by CVE-2024-8244?


## How do I fix CVE-2024-8244?

Apply the vendor's patch.

## Is CVE-2024-8244 being exploited?

There is no known exploitation of CVE-2024-8244 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8244 and fix it if it is affected.

What it is: CVE-2024-8244 is a low-severity vulnerability in Go standard library path/filepath, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8244 in the wild and no public exploit code.

Affected product: Go standard library path/filepath. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8244/ (Markdown: https://insights.sbomify.com/CVE-2024-8244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8244
- OSV: https://osv.dev/vulnerability/CVE-2024-8244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8244/
Summaries are generated and may contain mistakes; the official description above is the record.