# CVE-2026-61371: Path traversal in n/a

> An attacker can overwrite arbitrary files via symlink following in AVML, leading to data modification before input validation completes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-qm7h-f635-h2r6

## What is CVE-2026-61371?

CVE-2026-61371 is a high-severity path traversal vulnerability in n/a, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft AVML before 0.17.0 could follow a symlink when opening a destination output path on Unix, allowing truncation/overwrite of the symlink target. The destructive effect is performed at open-time via O_TRUNC, and can happen before full input validation completes (“truncation-before-validation”).

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-61371?


## How do I fix CVE-2026-61371?

No fix has been published for CVE-2026-61371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61371 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61371 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61371 and fix it if it is affected.

What it is: CVE-2026-61371 is a high-severity path traversal vulnerability in n/a, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61371 exists.

Affected product: n/a. 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-2026-61371/ (Markdown: https://insights.sbomify.com/CVE-2026-61371/index.md)
```

## Sources

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

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