CVE 8.8 HIGH

Apache Camel: Camel-Infinispan: Unsafe Deserialization in Remote Aggregation Repository_CVE-2026-40858

8.8 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 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.

AI Analysis

Arbitrary code execution due to unsafe deserialization in the camel-infinispan component's ProtoStream-based remote aggregation repository

Basic Information

ID CVE-2026-40858
Source apache
Published Apr 27, 2026 at 09:38
Modified Apr 27, 2026 at 14:10

Affected Product

Vendor Apache Software Foundation
Product Apache Camel
Version 4.0.0
Affected Versions Apache Software Foundation Apache Camel 4.0.0
Apache Software Foundation Apache Camel 4.15.0
Apache Software Foundation Apache Camel 4.19.0

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor Apache Software Foundation
Product Apache Camel
Version 4.0.0, 4.15.0, 4.19.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.