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

> Authenticated users can access git repositories outside the configured root directory due to missing path validation in Apache MINA SSHD's git module.

- **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:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-48827, GHSA-mw4m-qhpg-j82m, UBUNTU-CVE-2026-48827

## What is CVE-2026-48827?

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

### Official description

Path traversal vulnerability in Apache MINA SSHD bundle sshd-git. Lack of path validation in git-upload-pack, git-receive-pack, and other git operations allows users authenticated over SSH access to git repositories outside the configured git server root directory.

Applications are affected if they use org.apache.sshd:sshd-git. Applications not using sshd-git are not affected.

Users are advised to upgrade affected applications to Apche MINA SSHD 2.18.0, which fixes the issue.

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

We would like to point out that a professional git server should not rely solely on file system layout and permissions, but should implement additional security controls to govern access to git repositories and operations allowed on particular git repositories.

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

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

4 open source packages ship an affected version, including org.apache.sshd:sshd-git. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.sshd:sshd-git` | Maven | All versions | 2.18.0 |
| `org.apache.sshd:sshd-git` | Maven | All versions | 2.18.0 |
| `org.apache.sshd:sshd-git` | Maven | From 3.0.0-M1 | 3.0.0-M4 |
| `org.apache.sshd:sshd-git` | Maven | From 3.0.0-M1 | 3.0.0-M4 |

Products: Apache Mina Sshd.

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

Upgrade org.apache.sshd:sshd-git to a fixed version for your release line: 2.18.0 or 3.0.0-M4.

## Is CVE-2026-48827 being exploited?

There is no known exploitation of CVE-2026-48827 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-56623](https://insights.sbomify.com/CVE-2026-56623/): Apache MINA SSHD: Path traversal in org.apache.sshd:sshd-git on Windows (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-48827 and fix it if it is affected.

What it is: CVE-2026-48827 is a high-severity path traversal vulnerability in Apache MINA SSHD, published on 1 Jun 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-48827 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.sshd:sshd-git (Maven): affected all versions; fixed in 2.18.0
- org.apache.sshd:sshd-git (Maven): affected all versions; fixed in 2.18.0
- org.apache.sshd:sshd-git (Maven): affected from 3.0.0-M1; fixed in 3.0.0-M4
- org.apache.sshd:sshd-git (Maven): affected from 3.0.0-M1; fixed in 3.0.0-M4

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

## Sources

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

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