EUVD-2026-25808
GHSA-4xwx-hvv7-7prj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain write access to Infinispan cache
-
DeliveryCraft malicious serialized Java gadget
-
ExploitInject object into aggregation repository key
-
ExecutionCamel get/recover reads entry
-
PersistObjectInputStream deserializes without filter
-
ImpactGadget chain executes arbitrary code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The application must use the camel-infinispan ProtoStream-based remote aggregation repository (InfinispanRemoteAggregationRepository) backed by a remote Infinispan cache, and the attacker must have write access to that cache to insert a crafted serialized object; exploitation then fires on a normal get or recover operation. It is further limited by the need for a suitable Java deserialization gadget chain on the application classpath and by the PR:L requirement (cache-write access is not granted to fully unauthenticated outsiders in a properly secured deployment). It is NOT reachable against a default Camel install that does not use the Infinispan remote aggregation repository. |
| Impact | The CVSS 3.1 base score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting network reach and total confidentiality/integrity/availability loss, but the real-world picture is more nuanced. Exploitation is gated by a concrete prerequisite - the attacker must be able to write to the shared Infinispan cache - captured by PR:L and consistent with CISA SSVC (Exploitation: none, Automatable: no, Technical Impact: total). EPSS is very low at 0.08% (24th percentile) and the CVE is NOT in CISA KEV, so despite publicly available exploit code the signals point to a serious-but-not-yet-mass-exploited issue: 'Automatable: no' plus the cache-write precondition make this a targeted risk against specific Camel deployments rather than internet-wide scanning. Caveat: successful RCE additionally depends on a usable gadget chain on the classpath, which CVSS AC:L does not fully capture - verify your dependency set when prioritizing. |
| Exploit ScenarioDerived | An attacker who has gained write access to the Infinispan data grid shared by a Camel application (for example a compromised co-tenant service or leaked cache credentials) stores a crafted serialized Java object under a key the aggregation repository will read. When Camel next performs a normal get or recover on the aggregation repository, ObjectInputStream deserializes the payload, triggers a gadget chain on the classpath, and runs attacker code with the application's privileges. Publicly available POC code for this deserialization class lowers the effort required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 24, 2026
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.
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
4DescriptionCVE.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.
Blast Radius
ecosystem impact- 10 maven packages depend on org.apache.camel:camel-infinispan (5 direct, 5 indirect)
Ecosystem-wide dependent count for version 4.0.0.
Articles & Coverage 1
Executive ViewAI
Apache Camel's infinispan component contains a deserialization vulnerability allowing remote code execution when processing cache data through the ProtoStream-based remote aggregation repository. Publicly available exploit code exists; any attacker with write access to the backing Infinispan cache can execute arbitrary code within the application context. This threatens data confidentiality, system availability, and enables lateral movement for organizations relying on this component.
Apply vendor patch. Until patches are deployed, implement network-level access controls restricting write operations to the Infinispan cache, enforce authentication and authorization on all cache endpoints, and deploy continuous monitoring on cache write operations to detect exploitation attempts.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
Exploit-DB