CVE-2026-77185

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-30. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Authentication bypass in sshd-core in Apache MINA SSHD versions 2.0.0 to 2.19.0 and 3.0.0-M1 to 3.0.0-M5 for a certain (presumed rare) way to implement an SSH server.

Apache MINA SSHD is a Java library for client- and server-side SSH. In the server part of the library, a mechanism to perform "asynchronous authentication" exists. A server implemented with Apache MINA SSHD must contain explicit code to make use of this feature. The implementation of this feature was flawed and could potentially lead to skipping checking the signature in public-key or hostbased authentication, or returning a wrong result.

Users are recommended to upgrade to Apache MINA SSHD 2.20.0 or 3.0.0-M6, which fix the logic error and which additionally forbid the use of this "asynchronous authentication" mechanism with the public-key or hostbased authentication schemes: if used, the SSH session will be closed and the server will log an entry indicating that asynchronous authentication may be used only with password or keyboard-interactive authentication.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 30, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-77185(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libmina-sshd-java2.13.2-2, 2.13.2-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libmina-sshd-java2.13.2-2, 2.13.2-3
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 46× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 07:27 UTCGHSA enrichment
  2. 2026-10-05 03:41 UTCGHSA enrichment
  3. 2026-10-04 23:54 UTCEG score recompute
  4. 2026-10-04 23:54 UTCGHSA enrichment
  5. 2026-10-04 23:22 UTCEPSS rescore
  6. 2026-10-04 20:08 UTCGHSA enrichment
  7. 2026-10-04 16:20 UTCGHSA enrichment
  8. 2026-10-04 12:34 UTCGHSA enrichment
  9. 2026-10-04 08:48 UTCGHSA enrichment
  10. 2026-10-04 05:01 UTCGHSA enrichment
  11. 2026-10-04 01:15 UTCGHSA enrichment
  12. 2026-10-03 21:29 UTCGHSA enrichment
  13. 2026-10-03 17:42 UTCEG score recompute
  14. 2026-10-03 17:42 UTCGHSA enrichment
  15. 2026-10-03 14:26 UTCEPSS rescore
  16. 2026-10-03 13:56 UTCGHSA enrichment
  17. 2026-10-03 10:09 UTCGHSA enrichment
  18. 2026-10-03 06:23 UTCGHSA enrichment
  19. 2026-10-03 02:37 UTCGHSA enrichment
  20. 2026-10-02 22:51 UTCGHSA enrichment
  21. 2026-10-02 19:05 UTCEG score recompute
  22. 2026-10-02 19:05 UTCGHSA enrichment
  23. 2026-10-02 15:19 UTCGHSA enrichment
  24. 2026-10-02 11:31 UTCGHSA enrichment
  25. 2026-10-02 07:35 UTCGHSA enrichment
Show 21 more
  1. 2026-10-02 03:49 UTCGHSA enrichment
  2. 2026-10-02 00:01 UTCGHSA enrichment
  3. 2026-10-01 19:54 UTCEG score recompute
  4. 2026-10-01 19:54 UTCGHSA enrichment
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-10-01 16:08 UTCGHSA enrichment
  7. 2026-10-01 12:22 UTCGHSA enrichment
  8. 2026-10-01 08:34 UTCGHSA enrichment
  9. 2026-10-01 04:48 UTCGHSA enrichment
  10. 2026-10-01 00:57 UTCGHSA enrichment
  11. 2026-09-30 21:11 UTCGHSA enrichment
  12. 2026-09-30 17:25 UTCEG score recompute
  13. 2026-09-30 17:25 UTCGHSA enrichment
  14. 2026-09-30 16:56 UTCEG score recompute
  15. 2026-09-30 16:56 UTCGHSA enrichment
  16. 2026-09-30 16:23 UTCGHSA enrichment
  17. 2026-09-30 15:05 UTCEG score recompute
  18. 2026-09-30 15:05 UTCGHSA enrichment
  19. 2026-09-30 10:31 UTCEG score recompute
  20. 2026-09-30 09:53 UTCEG score recompute
  21. 2026-09-30 09:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77185?
CVE-2026-77185 is a critical vulnerability published on September 30, 2026. Authentication bypass in sshd-core in Apache MINA SSHD versions 2.0.0 to 2.19.0 and 3.0.0-M1 to 3.0.0-M5 for a certain (presumed rare) way to implement an SSH server. Apache MINA SSHD is a Java library for client- and server-side SSH. In the server part of the library, a mechanism to perform…
When was CVE-2026-77185 disclosed?
CVE-2026-77185 was first published on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77185 actively exploited?
CVE-2026-77185 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77185?
CVE-2026-77185 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77185?
No fix for CVE-2026-77185 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-77185 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77185

Explore →

Is Your Infrastructure Affected by CVE-2026-77185?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.