What is the CVSS score of CVE-2026-40858?

CVE-2026-40858 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Apache Camel are affected by CVE-2026-40858?

Apache Camel's infinispan component contains a deserialization vulnerability allowing remote code execution when processing cache data through the ProtoStream-based remote aggregation repository.. A patch is available.

Is there a public PoC exploit available for CVE-2026-40858?

Yes, a public proof-of-concept exploit is available for CVE-2026-40858. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-40858?

Within 24 hours, identify all systems running Apache Camel with the camel-infinispan component and restrict network access to the Infinispan cache endpoint to authorized systems only. Within 7 days, apply the patch available per vendor advisory to all affected Apache Camel deployments, verifying the specific patched version from the official vendor security bulletin. Within 30 days, audit access logs for unauthorized cache write attempts, implement real-time alerting on cache write operations, and revalidate network segmentation around Infinispan infrastructure.

Apache Camel CVE-2026-40858

EUVD-2026-25808 HIGH

Deserialization of Untrusted Data (CWE-502)

2026-04-27 apache

GHSA-4xwx-hvv7-7prj

Java Atlassian Deserialization RCE Apache Apache Camel

8.8

CVSS 3.1 · Vendor: apache

Severity by source

Vendor (apache) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.5 HIGH

Network-reachable via the cache with PR:L for required cache-write access, but AC:H because exploitation also depends on a usable gadget chain on the classpath; full C/I/A loss on RCE.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 24, 2026 - 02:05 vuln.today

Patch released

Apr 28, 2026 - 19:41 nvd

Patch available

CVSS changed

Apr 27, 2026 - 15:22 NVD

8.8 (HIGH)

Patch available

Apr 27, 2026 - 11:01 EUVD

EUVD ID Assigned

Apr 27, 2026 - 10:00 euvd

EUVD-2026-25808

CVE Published

Apr 27, 2026 - 09:38 nvd

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

13 maven packages depend on org.apache.camel:camel-infinispan (5 direct, 8 indirect)

Ecosystem-wide dependent count for version 4.0.0.

DescriptionCVE.org

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.

Articles & Coverage 1

POC Apache Camel 4.18.0: Three Critical RCE Vulnerabilities with Working PoC Exploits (CVE-2026-33453, CVE-2026-40473, CVE-2026-40858) Apr 27, 2026

AnalysisAI

Unsafe Java deserialization in Apache Camel's camel-infinispan component allows arbitrary code execution when the ProtoStream-based remote aggregation repository reads objects from an Infinispan cache using java.io.ObjectInputStream with no ObjectInputFilter applied. Any attacker able to write to the backing Infinispan cache can plant a malicious serialized gadget that executes in the application context during routine get/recover operations. Publicly available exploit code exists, though EPSS is low (0.08%) and there is no evidence of active exploitation.

Technical ContextAI

Apache Camel is a widely used Java integration framework whose aggregator EIP can persist in-flight exchanges to an external repository. The camel-infinispan component provides an InfinispanRemoteAggregationRepository that stores serialized exchange state in a remote Infinispan (JBoss Data Grid) key/value cache, using ProtoStream for marshalling but falling back to native Java serialization (ObjectInputStream) for payload objects. Because no ObjectInputFilter (JEP 290 allow/deny list) is installed, the classic CWE-502 (Deserialization of Untrusted Data) condition is met: any serialized object graph read from the cache is fully reconstructed, so a Java gadget chain present on the application classpath (e.g. commons-collections, Spring) can be driven to code execution. This is the same defect class Camel previously patched in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747, indicating a recurring pattern of unfiltered ObjectInputStream use across Camel components.

RemediationAI

Vendor-released patch: upgrade to Apache Camel 4.20.0, which fixes the issue; users on the 4.14.x LTS stream should upgrade to 4.14.7 and users on the 4.18.x stream to 4.18.2. Track the fix commits via JIRA CAMEL-23322 and the advisory at https://camel.apache.org/security/CVE-2026-40858.html; Red Hat consumers should apply RHSA-2026:17668 and RHSA-2026:22453. If immediate patching is not possible, restrict and authenticate write access to the Infinispan cache so untrusted parties cannot insert entries (this removes the injection vector but requires cache ACL/credential changes), isolate the Infinispan cluster on a trusted network segment, and where feasible install a JVM-wide ObjectInputFilter (jdk.serialFilter) allow-listing only expected Camel/exchange classes - noting an overly strict filter can break legitimate aggregation deserialization and must be tested against your exchange payloads.