# CVE-2026-54336: JumpServer: KoKo Web Terminal SFTP Path Traversal on Authorized Asset

> Authenticated users with SFTP permissions can traverse directories to read, modify, or delete files on authorized assets via the KoKo Web Terminal.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-x6rg-36j6-76vr

## What is CVE-2026-54336?

CVE-2026-54336 is a medium-severity path traversal vulnerability in jumpserver, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JumpServer is an open source bastion host and an operation and maintenance security audit system. From 4.8.0 until 4.10.17, an authenticated user with SFTP permission to an authorized asset can submit crafted traversal paths through the KoKo Web Terminal SFTP feature, causing AssetDir.GetRealPath() in pkg/srvconn/sftp_asset.go to resolve paths outside the intended SFTP root and permit read, list, write, rename, or delete operations under the configured backend account on that asset. This issue is fixed in version 4.10.17.

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

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


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

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

## Is CVE-2026-54336 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54336 is a medium-severity path traversal vulnerability in jumpserver, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54336 exists.

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

## Sources

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

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