CVE-2026-24656: Apache Karaf · Deserialization of Untrusted Data
Affects Apache KarafSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 2.12.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.12.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 26 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Apache Karaf and Apache Software Foundation/org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socket and org.apache.karaf/apache-karaf-decanter to 2.12.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Karaf | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socketpkg:maven/Apache Software Foundation/org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socketOther threats | Affected
| Fixed in
|
Mavenorg.apache.karaf/apache-karaf-decanterpkg:maven/org.apache.karaf/apache-karaf-decanterOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately upgrade Apache Karaf Decanter to version 2.12.0 or later, which contains the fix for this vulnerability.
- If upgrading is not immediately possible, disable the Decanter log socket collector component to eliminate exposure.
- Restrict network access to port 4560 using firewall rules or network segmentation to limit connections only to trusted hosts.
- Review and harden the 'allowed classes' deserialization property configuration to ensure it does not allow bypasses; consider disabling it if not required.
- Monitor network traffic and logs for unusual connections or serialized payloads targeting port 4560.
- Implement intrusion detection systems (IDS) or endpoint detection and response (EDR) solutions to detect exploitation attempts.
- Conduct regular security assessments and penetration tests focusing on deserialization vulnerabilities in custom or third-party components.
- Educate development and operations teams about the risks of deserialization of untrusted data and secure coding practices.
- Maintain an inventory of Apache Karaf deployments to identify which systems have Decanter installed and prioritize remediation accordingly.
Description
Deserialization of Untrusted Data vulnerability in Apache Karaf Decanter. The Decanter log socket collector exposes the port 4560, without authentication. If the collector exposes allowed classes property, this configuration can be bypassed. It means that the log socket collector is vulnerable to deserialization of untrusted data, eventually causing DoS. NB: Decanter log socket collector is not installed by default. Users who have not installed Decanter log socket are not impacted by this issue. This issue affects Apache Karaf Decanter before 2.12.0. Users are recommended to upgrade to version 2.12.0, which fixes the issue.