Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Network-reachable and unauthenticated with low complexity (AV:N/AC:L/PR:N/UI:N), but only partial impact given an information-disclosure-oriented input-validation flaw, so C/I/A each Low.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
5Blast Radius
ecosystem impact- 6 maven packages depend on org.apache.camel:camel-langchain4j-tools (3 direct, 3 indirect)
Ecosystem-wide dependent count for version 4.8.0.
DescriptionCVE.org
Improper Input Validation vulnerability in Apache Camel.
This issue affects Apache Camel: from 4.8.0 through 4.18.2, from 4.19.0 through 4.20.0.
Users are recommended to upgrade to version 4.18.3, 4.21.0, which fixes the issue.
AnalysisAI
Improper input validation in Apache Camel versions 4.8.0 through 4.18.2 and 4.19.0 through 4.20.0 allows remote unauthenticated attackers to send crafted input that the framework fails to validate, yielding limited information disclosure and partial integrity/availability impact per the CVSS vector. The flaw is reported directly by the Apache Software Foundation and is fixed in 4.18.3 and 4.21.0; there is no public exploit identified at time of analysis and it is not on the CISA KEV list. The moderate 7.3 (High) score reflects easy network reachability but limited per-impact severity (C:L/I:L/A:L).
Technical ContextAI
Apache Camel is a widely deployed open-source Java integration framework implementing Enterprise Integration Patterns, used to route and mediate messages between systems via hundreds of components and endpoints. The root cause is classified as CWE-20 (Improper Input Validation), meaning the framework accepts externally supplied input without adequately verifying that it conforms to expected structure, type, or constraints before processing it. The affected artifact is identified by CPE cpe:2.3:a:apache_software_foundation:apache_camel and, per the vendor tag, the practical consequence is Information Disclosure. Because Camel typically sits at trust boundaries between services, an input-validation gap in a component or header/parameter handling path can expose or alter data flowing through a route, though the exact vulnerable component is not detailed in the available advisory summary.
RemediationAI
Vendor-released patch: upgrade to Apache Camel 4.18.3 (for the 4.8.0-4.18.2 branch) or 4.21.0 (for the 4.19.0-4.20.0 branch), as recommended by the Apache advisory at https://camel.apache.org/security/CVE-2026-49042.html. Because the specific vulnerable component is not disclosed in the available summary, review that advisory to identify whether a particular Camel component, endpoint, or route is implicated and, if immediate patching is not possible, restrict or disable exposure of that route and place untrusted-facing Camel endpoints behind an authenticating gateway or input-filtering proxy that enforces strict schema/type validation on incoming messages - noting this may reject some legitimately malformed-but-tolerated traffic and requires knowledge of the exact affected input path. Given only Low impact metrics, upgrading during the normal maintenance window is a reasonable priority absent evidence of exploitation, but should be expedited for internet-exposed integrations.
More in Apache Camel
View allRemote code execution in Apache Camel's camel-coap component (versions 4.14.0-4.14.5, 4.18.0 before 4.18.1, and 4.19.0)
Unsafe Java deserialization in Apache Camel's camel-infinispan component allows arbitrary code execution when the ProtoS
Header-injection in the Apache Camel camel-atmosphere-websocket producer lets an external sender hijack WebSocket messag
Header-filter bypass in the Apache Camel Undertow component (4.11.0-4.14.8, 4.15.0-4.18.3, and 4.19.0-4.21.x) lets remot
Remote code execution in Apache Camel 3.18.0-4.14.5 and 4.15.0-4.18.1 stems from CXF and Knative HeaderFilterStrategy im
Message header injection in Apache Camel's camel-mail component (3.0.0 before 4.14.6 and 4.15.0 before 4.18.1) lets an a
Remote code execution via unsafe Java deserialization affects the camel-pqc component of Apache Camel 4.18.0-4.18.2 and
Unsafe Java deserialization in Apache Camel's camel-consul component (ConsulRegistry / ConsulRegistryUtils.deserialize)
Cypher injection in Apache Camel's camel-neo4j producer allows attackers who control JSON key names in the CamelNeo4jMat
Remote code execution in the Apache Camel camel-hazelcast component allows an attacker who can join or reach the Hazelca
Remote code execution in Apache Camel's camel-vertx-http component (4.0.0-4.14.7, 4.15.0-4.18.2, 4.19.0) arises when a p
Blind out-of-band data exfiltration in Apache Camel 4.14.0-4.20.x arises because the default ObjectInputFilter pattern b
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-41864
GHSA-hh8r-75r6-qrg9