dbcve.org
Mina SshdApplication · Apache

CVE-2026-48827

HIGH · 7.1 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 2.18.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in Apache MINA SSHD's sshd-git bundle where git-upload-pack, git-receive-pack, and other git operations lack path validation. This allows SSH-authenticated users to access git repositories outside the configured git server root directory by manipulating file paths.

MitigationUpgrade to Apache MINA SSHD version 2.18.0 (or 3.0.0-M4 for the upcoming major version) which contains the fix. Additionally, implement access control checks beyond filesystem permissions to govern which repositories users can access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mina SshdApplication
Affected:>= 2.0.0, < 2.18.0= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache MINA SSHD installation and version
    Search for sshd-core or sshd-git JAR files in your application dependencies (e.g., pom.xml, requirements.txt, lib directory) or run: java -jar <sshd-jar> --version. Check the version number against the affected ranges: >= 2.0.0 and < 2.18.0, or exactly 3.0.0.
    Affected if The installed version is 2.0.0 through 2.17.x, or is exactly 3.0.0 (including milestone versions M1-M3).
  2. Confirm sshd-git module is in use
    Look for the sshd-git artifact in your build configuration or verify that git repository serving functionality is enabled in your application. Check for imports of org.apache.sshd.git.* classes in your codebase.
    Affected if The sshd-git module is present and git repository serving is configured.
  3. Verify git operations are exposed
    Inspect your SSHD server configuration for enabled git commands: git-upload-pack, git-receive-pack, git-upload-archive, and other git service handlers. These are typically configured via SshGitModule or similar git-specific command factories.
    Affected if Git operations (git-upload-pack, git-receive-pack) are exposed via SSH.
  4. Check repository root directory configuration
    Review your SSHD git configuration to identify the configured repository root or base path. Look for properties like git.repositoryRoot, git.basePath, or similar configuration keys that define where repositories are served from.
    Affected if A repository root is configured and git operations are accessible to authenticated users without additional path validation layers.

You are affected if Apache MINA SSHD sshd-git bundle version is less than 2.18.0 (or is 3.0.0) and git operations are enabled, allowing authenticated SSH users to potentially access files outside the configured repository root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.18.0 or later
Fixed in 2.18.0
Interim mitigation

Upgrade to Apache MINA SSHD version 2.18.0 (or 3.0.0-M4 for the upcoming major version) which contains the fix. Additionally, implement access control checks beyond filesystem permissions to govern which repositories users can access.

Recommended fix High confidence

Apache MINA SSHD 2.18.0 (or 3.0.0-M4 for 3.x line users)

  1. Identify all applications and projects that depend on org.apache.sshd:sshd-git library
  2. For applications using MINA SSHD 2.x: Update the dependency version to 2.18.0 (org.apache.sshd:sshd-git:2.18.0)
  3. For applications using MINA SSHD 3.x milestones (M1-M3): Update the dependency version to 3.0.0-M4 (org.apache.sshd:sshd-git:3.0.0-M4)
  4. Rebuild the affected applications with the new dependency version
  5. Perform regression testing, particularly verifying git operations (git-upload-pack, git-receive-pack) cannot access files outside the configured repository root
  6. Deploy the updated applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mina Sshd Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48827 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data