CVE-2026-40858
Published: 27 April 2026
Description
The camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a remote Infinispan cache using java.io.ObjectInputStream without applying any ObjectInputFilter. An attacker who can write to the Infinispan cache used by a Camel application can inject a crafted serialized…
more
Java object that, when read during normal aggregation repository operations such as get or recover, results in arbitrary code execution in the context of the application. This issue affects Apache Camel: from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2. The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23322 refers to the various commits that resolved the issue, and have more details. This issue follows the same class of vulnerability previously addressed in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747.
Mitigating Controls (NIST 800-53 r5)AI
Directly mitigates the deserialization vulnerability by requiring timely remediation through upgrades to patched Apache Camel versions that apply ObjectInputFilter.
Mandates validation of untrusted inputs like serialized objects from the remote Infinispan cache to block malicious payloads prior to deserialization.
Enforces integrity verification of information from the Infinispan cache, helping to identify and prevent execution of tampered serialized objects leading to RCE.
Security SummaryAI
CVE-2026-40858 is a deserialization vulnerability in the camel-infinispan component of Apache Camel, specifically in its ProtoStream-based remote aggregation repository. The flaw occurs because data read from a remote Infinispan cache is deserialized using java.io.ObjectInputStream without applying any ObjectInputFilter, allowing malicious serialized objects to be processed. This issue affects Apache Camel versions from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, and from 4.19.0 before 4.20.0.
An attacker with write access to the Infinispan cache used by a Camel application can inject a crafted serialized Java object. When the application performs normal aggregation repository operations such as get or recover, the object is deserialized, leading to arbitrary code execution in the context of the Camel application process. The vulnerability has a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating network accessibility, low attack complexity, and low privileges required, with high impacts on confidentiality, integrity, and availability.
The Apache Camel security advisory at https://camel.apache.org/security/CVE-2026-40858.html recommends upgrading to version 4.20.0 to resolve the issue. Users on the 4.14.x LTS stream should upgrade to 4.14.7, and those on the 4.18.x stream to 4.18.2. Additional details, including resolution commits, are available in the associated JIRA ticket at https://issues.apache.org/jira/browse/CAMEL-23322. This vulnerability is classified under CWE-502 (Deserialization of Untrusted Data) and follows similar issues addressed in CVE-2024-22369, CVE-2024-23114, and CVE-2026-25747.
Details
- CWE(s)
Affected Products
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Deserialization vulnerability in network-accessible Apache Camel Infinispan component enables remote low-privilege attackers to inject malicious objects for arbitrary code execution, directly facilitating exploitation of public-facing applications, remote services, and privilege escalation.