# CVE-2026-56623: Apache MINA SSHD: Path traversal in org.apache.sshd:sshd-git on Windows

> Authenticated attackers can access git repositories outside the configured root directory on Windows servers using Apache MINA SSHD sshd-git.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-q57w-g8m3-937c, UBUNTU-CVE-2026-56623

## What is CVE-2026-56623?

CVE-2026-56623 is a high-severity path traversal vulnerability in Apache MINA SSHD, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path traversal on Windows in Apache MINA SSHD component sshd-git. Apache MINA SSHD is a Java library for client-side and server-side SSH.

A git server implemented with Apache MINA SSHD component sshd-git and running on Windows could allow an authenticated remote user access to git repositories outside of the configured server-side root directory. The path validation applied for CVE-2026-48827 in Apache MINA SSHD 2.18.0 and 3.0.0-M4 was partly ineffective for Servers running on Windows.

Applications are affected if they use org.apache.sshd:sshd-git to implement a git server and run on Windows. Applications not using sshd-git or not running on Windows are not affected.

Users are advised to upgrade affected applications to Apache MINA SSHD 2.19.0, which fixes the issue.

The issue also is present in the pre-release milestones 3.0.0-M1 to 3.0.0-M4 for a new upcoming new major version 3.0.0. Again, applications are affected only if they use sshd-git and run on Windows. Upgrade affected applications to 3.0.0-M5.

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

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

It affects 1 product.


Products: Apache Mina Sshd.

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

Upgrade to a fixed version.

## Is CVE-2026-56623 being exploited?

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

## Other vulnerabilities in Apache MINA SSHD

- [CVE-2026-56452](https://insights.sbomify.com/CVE-2026-56452/): Apache MINA SSHD: Path traversal in SCP file reception (high 7.5)
- [CVE-2026-56624](https://insights.sbomify.com/CVE-2026-56624/): Apache MINA SSHD: SSH certificate options lack validations (high 7.3)
- [CVE-2026-48827](https://insights.sbomify.com/CVE-2026-48827/): Apache MINA SSHD: Path traversal in org.apache.sshd:sshd-git (high 7.1)
- [CVE-2024-41909](https://insights.sbomify.com/CVE-2024-41909/): Apache MINA SSHD: integrity check bypass (medium 5.9)
- [CVE-2019-6111](https://insights.sbomify.com/CVE-2019-6111/): Path traversal in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56623 is a high-severity path traversal vulnerability in Apache MINA SSHD, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56623 in the wild and no public exploit code.

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

## Sources

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

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