Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS

Apache Software Foundation

Apache Mina SSHD

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-77185 30 Sep 2026 Apache MINA SSHD: 2.0.0 < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-93994 30 Sep 2026 Apache MINA SSHD: < 2.20.0, 3.0.0-M1 < 3.0.0-M6 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-94053 30 Sep 2026 Apache MINA SSHD: 1.2.0 < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-93995 30 Sep 2026 Apache MINA SSHD: < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-93996 30 Sep 2026 Apache MINA SSHD: < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-94002 30 Sep 2026 Apache MINA SSHD: 0.9.0 < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-94029 30 Sep 2026 Apache MINA SSHD: 1.0.0 < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-94052 30 Sep 2026 Apache MINA SSHD: 1.2.0 < 2.20.0, 3.0.0-M1 < 3.0.0-M6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56623 20 Jul 2026 2.0.0 ≤ 2.18.0; 3.0.0-M1 ≤ 3.0.0-M4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56624 20 Jul 2026 2.0.0 ≤ 2.18.0; 3.0.0-M1 ≤ 3.0.0-M4 It is recommended that existing users of Red Hat OpenShift Developer Tools - OpenShift Jenkins 4.12 upgrade to the latest. This image uses java-21-openjdk as the default JDK. java-25-openjdk is not available in rhel8 images. java-17-openjdk is removed. Update reference ↗
CVE-2026-58624 20 Jul 2026 2.0.0 ≤ 2.18.0; 3.0.0-M1 ≤ 3.0.0-M4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56452 20 Jul 2026 ≤ 2.18.0; 3.0.0-M1 ≤ 3.0.0-M4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48827 1 Jun 2026 2.0.0 ≤ 2.17.1; 3.0.0-M1 ≤ 3.0.0-M3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41909 12 Aug 2024 ≤ 2.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35887 10 Jul 2023 1.0 < 2.10 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2022-45047 16 Nov 2022 unspecified ≤ 2.9.1 Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2021-30129 12 Jul 2021 2.0.0 < Apache Mina SSHD* Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.