CVE-2026-48827 — sshd-git
HIGHCVE-2026-48827 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: Path traversal in org.apache.sshd:sshd-git
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 CVE-2026-48827.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-48827 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.sshd:sshd-git☕org.apache.sshd:sshd-gitReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.sshd:sshd-git | all versions | 2.18.0org.apache.sshd:sshd-git:2.18.0 |
| ☕Maven | org.apache.sshd:sshd-git | ≥ 3.0.0-M1&&< 3.0.0-M4 | 3.0.0-M4org.apache.sshd:sshd-git:3.0.0-M4 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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 CVE-2026-48827 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-48827 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-48827. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
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 CVE-2026-48827 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-48827 in your dependencies?
O3 Security finds CVE-2026-48827 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.