SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-56623Public Intelligence Dossier
Source: apache · Limited verification•Last verified: •Collection Degraded
CVE-2026-56623Unknown / EvaluatingHIGH (raw)CVSS 7.1CWE-22

Path traversal on Windows in Apache MINA SSHD component sshd-git

Published: 21 Jul 2026•Last updated: 25 Oct 2026, 01:40 AM IST•Source identifier: security@apache.org
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
7.1HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Metric sourcesecurity@apache.org
EPSS probability
0.9%0.009
Percentile59th
Weakness type
CWE-22
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Path traversal on Windows in Apache MINA SSHD component sshd-git. Apache MINA SSHD is a Java library for client-side and server-side SSH. A git server implemented with Apache MINA SSHD component sshd-git and running on Windows could allow an authenticated remote user access to git repositories outside of the configured server-side root directory. The path validation applied for CVE-2026-48827 in Apache MINA SSHD 2.18.0 and 3.0.0-M4 was partly ineffective for Servers running on Windows. Applications are affected if they use org.apache.sshd:sshd-git to implement a git server and run on Windows. Applications not using sshd-git or not running on Windows are not affected. Users are advised to upgrade affected applications to Apache MINA SSHD 2.19.0, which fixes the issue. The issue also is present in the pre-release milestones 3.0.0-M1 to 3.0.0-M4 for a new upcoming new major version 3.0.0. Again, applications are affected only if they use sshd-git and run on Windows. Upgrade affected applications to 3.0.0-M5.

SOC priority

High

Actively exploited (source statement)

Unknown

Publicly disclosed

Unknown

Risk basis: Microsoft or Microsoft-managed product relevance; HIGH severity; Source severity; no confirmed exploitation signal

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • apache mina sshd · >= 2.0.0 < 2.19.0; 3.0.0 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched path-traversal (CWE-22)

Exposure

  1. Locate affected deployments and the path-handling endpoint named by the advisory.Telemetry: Application access logs · The affected path must come from the source, not the CWE alone. · Rule path-traversal

Exploitation evidence

  1. Review requests to that endpoint for traversal encodings and unusual file responses.Telemetry: Application access logs · Such patterns are a hypothesis to validate against normal traffic. · Rule path-traversal

Response

  1. Verify the source-stated fix and retest the affected path.Telemetry: Application change records · The exact remediation depends on the source advisory. · Rule path-traversal

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security@apache.org
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:a:apache:mina_sshd:*:*:*:*:*:*:*:*, cpe:2.3:a:apache:mina_sshd:3.0.0:m1:*:*:*:*:*:*, cpe:2.3:a:apache:mina_sshd:3.0.0:m2:*:*:*:*:*:*, cpe:2.3:a:apache:mina_sshd:3.0.0:m3:*:*:*:*:*:*, cpe:2.3:a:apache:mina_sshd:3.0.0:m4:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

Evidence & Provenance

2 public sources

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-56623
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-56623
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-56623"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.