# CVE-2026-67397: Path traversal in Plesk

> Local attackers can exploit path traversal in Plesk to execute arbitrary code with root privileges, requiring immediate patching.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-pm4q-j54p-8jgq

## What is CVE-2026-67397?

CVE-2026-67397 is a high-severity path traversal vulnerability in WebPros Plesk, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Path traversal in Plesk 18.0.79.9 and earlier and 18.0.80 through 18.0.80.5 allows local users to execute arbitrary code as root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-67397 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67397 is a high-severity path traversal vulnerability in WebPros Plesk, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67397 in the wild and no public exploit code.

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

## Sources

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

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