Skip to content
Noroxi
CVE-2026-48827· NVD / CVE Program· CNA apache

Apache MINA SSHD: Path traversal in org.apache.sshd:sshd-git

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 1, 2026
Updated
Jul 22, 2026
EPSS
0.8% · 55th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · apache
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
apachemina sshd

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache mina sshd2.0.0 and later · before 2.18.0
  • apache mina sshd3.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache MINA SSHD

    • 2.0.0 and later · up to and including 2.17.1affected · maven
    • 3.0.0-M1 and later · up to and including 3.0.0-M3affected · maven

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13libmina-sshd-javaall versions—
Mavenorg.apache.sshd:sshd-gitfrom 3.0.0-M1 · before 3.0.0-M43.0.0-M4
Mavenorg.apache.sshd:sshd-gitbefore 2.18.02.18.0
openSUSE:Tumbleweedapache-sshdbefore 2.18.0-1.12.18.0-1.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7apache-sshdbefore 2.18.0-150200.5.11.12.18.0-150200.5.11.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7jpgpjbefore 1.3-150200.5.3.11.3-150200.5.3.1

Other highest-scoring records for the same primary product.

  • CVE-2026-56452Apache MINA SSHD: Path traversal in SCP file reception
    30Monitor
  • CVE-2026-56624Apache MINA SSHD: SSH certificate options lack validations
    29Monitor
  • CVE-2026-56623Apache MINA SSHD: Path traversal in org.apache.sshd:sshd-git on Windows
    28Monitor
  • CVE-2024-41909Apache MINA SSHD: integrity check bypass
    23Monitor
  • CVE-2026-58624Apache MINA SSHD: Remote execution of JGit commands can write files on the server
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.apache.sshd:sshd-git2.18.0Package registry (OSV)
Maven:org.apache.sshd:sshd-git3.0.0-M4Package registry (OSV)
opensuse:apache-sshd2.18.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:apache-sshd2.18.0-150200.5.11.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:jpgpj1.3-150200.5.3.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5645249 days apartApache MINA SSHD: Path traversal in SCP file reception
    30Monitor
  • CVE-2026-5662349 days apartApache MINA SSHD: Path traversal in org.apache.sshd:sshd-git on Windows
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records