Apache Karaf
Apache Software Foundation- Product type
- Other
- Catalog vulnerabilities
- 9
Severity across 9 analyzed records
Verify to analyze this security profile
en
Severity across 9 analyzed records
Verify to analyze this security profile
As of 09/19/2026, within CyStack's analyzed data, Apache Karaf has 1 security vulnerability published in the last 90 days. Of these, 1 is rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Apache Karaf and determine which vulnerabilities affect that version.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-92230Apache Karaf: Improper release of ClassLoader references via static ThreadLocal caching | Exploitation statusNot known exploited | FixYes | Published09/17/2026 | SeverityHigh |
CVE-2026-24656Apache Karaf: Decanter log-socket collector has deserialization vulnerability | Exploitation statusNot known exploited | FixYes | Published01/26/2026 | SeverityLow |
CVE-2022-40145Apache Karaf: JDBC JAAS LDAP injection | Exploitation statusNot known exploited | FixYes | Published12/21/2022 | SeverityCritical |
CVE-2022-22932Path traversal flaws | Exploitation statusNot confirmed | FixYes | Published01/26/2022 | SeverityUnknown |
CVE-2021-41766Insecure Java Deserialization in Apache Karaf | Exploitation statusNot confirmed | FixYes | Published01/26/2022 | SeverityUnknown |
CVE-2018-11788 | Exploitation statusNot confirmed | FixYes | Published01/07/2019 | SeverityUnknown |
CVE-2018-11787 | Exploitation statusNot confirmed | FixNot confirmed | Published09/18/2018 | SeverityUnknown |
CVE-2018-11786 | Exploitation statusNot confirmed | FixNot confirmed | Published09/18/2018 | SeverityUnknown |
CVE-2016-8750 | Exploitation statusNot confirmed | FixNot confirmed | Published02/19/2018 | SeverityUnknown |