Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-mw4m-qhpg-j82m — sshd-git

HIGH

GHSA-mw4m-qhpg-j82m is a high-severity (CVSS 7.1) Path Traversal vulnerability in org.apache.sshd:sshd-git. A fix is available for org.apache.sshd:sshd-git — see the affected versions and patch details below.

Apache MINA SSHD bundle sshd-git has a path traversal vulnerability

Also known asCVE-2026-48827
Published
Jun 1, 2026
Updated
Jul 9, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mw4m-qhpg-j82m.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-mw4m-qhpg-j82m by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.apache.sshd:sshd-git☕org.apache.sshd:sshd-git

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

There is a 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.

Apache MINA SSHD bundle sshd-git 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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.sshd:sshd-gitall versions2.18.0org.apache.sshd:sshd-git:2.18.0
☕Mavenorg.apache.sshd:sshd-git≥ 3.0.0-M1&&< 3.0.0-M43.0.0-M4org.apache.sshd:sshd-git:3.0.0-M4

Affected Products

1 product · 4 configurations
Application
mina sshdapache
≥ 2.0.0 && < 2.18.0
1 version
3.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sshd:sshd-git, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.sshd:sshd-git to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw4m-qhpg-j82m is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
To mitigate this issue, ensure the Git server environment is configured with strict access controls and isolation. Restrict operating system user accounts used for SSH Git access to their intended repository roots, potentially using chroot jails or similar mechanisms. Implement additional authorization layers to govern access to Git repositories and operations, preventing authenticated users from traversing outside the designated server root directory. Review and harden file system permissions to limit access to sensitive directories.
Source: Red Hat security advisory for GHSA-mw4m-qhpg-j82m (CC BY 4.0)

Frequently Asked Questions

There is a 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
O3 Security · Impact-Aware SCA

Is GHSA-mw4m-qhpg-j82m in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-mw4m-qhpg-j82m: sshd-git (High 7.1) | O3 Security