CVE-2026-40858: Apache Camel: Camel-Infinispan: Unsafe Deserialization in Remote Aggregation Repository
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 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.
Security readout for executives and security teams
Plain-English summary
A compromised or untrusted writer to an application’s remote Infinispan cache could place malicious data that Apache Camel later processes, potentially running attacker-controlled code with the application’s permissions. Exposure is limited to affected Camel versions using the camel-infinispan remote aggregation repository; merely running Camel is insufficient.
Executive priority
Prioritize rapid remediation for internet-facing or high-value applications where untrusted or compromised identities can write to the relevant cache. Successful exploitation could fully compromise the Camel application and disrupt dependent integrations. Lower the priority only after confirming the vulnerable component or remote aggregation repository is absent, or cache writes are strongly constrained.
Technical view
The ProtoStream-based remote aggregation repository uses java.io.ObjectInputStream without an ObjectInputFilter. Crafted serialized Java objects written into the associated Infinispan cache can trigger arbitrary code execution when normal repository operations, including get or recover, deserialize them. Affected ranges are 4.0.0–4.14.6, 4.15.0–4.18.1, and 4.19.x before 4.20.0.
Likely exposure
Highest where an affected camel-infinispan dependency backs a remote aggregation repository and an attacker can write to its Infinispan cache. Network reachability alone does not establish exploitability; cache write authorization or another cache-write path is required. Applications not using this component and repository mode are not shown as exposed by the supplied evidence.
Exploitation context
CVSS 3.1 is 8.8: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation. It identifies cache write access as the necessary attacker capability.
Researcher notes
This is CWE-502 unsafe deserialization and follows the same vulnerability class as CVE-2024-22369, CVE-2024-23114, and CVE-2026-25747. Assessment should distinguish package presence from reachable behavior: vulnerable deserialization occurs when repository operations read attacker-controlled cache entries. The supplied sources do not document public proof-of-concept availability, exploitation telemetry, or specific detection indicators.
Mitigation direction
Upgrade 4.14.x deployments to 4.14.7 or later within that supported stream.
Upgrade 4.18.x deployments to 4.18.2 or later within that supported stream.
Upgrade other affected deployments to Apache Camel 4.20.0 or later.
Until upgraded, tightly restrict write access to the application’s Infinispan cache.
Validation and detection
Inventory org.apache.camel:camel-infinispan versions in applications and resolved dependency trees.
Confirm whether each application configures the ProtoStream-based remote aggregation repository.
Verify affected deployments now resolve to 4.14.7, 4.18.2, or 4.20.0 as applicable.
Review Infinispan authentication and authorization to identify principals capable of writing to the relevant cache.
After upgrading, exercise normal aggregation get and recovery workflows through regression testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.