Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Vendor-assigned network, unauthenticated, low-complexity path with bounded Low impact retained absent any description detail contradicting AV:N/PR:N, though component specifics are unverifiable.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
5Blast Radius
ecosystem impact- 11 maven packages depend on org.apache.camel:camel-couchbase (5 direct, 6 indirect)
Ecosystem-wide dependent count for version 4.0.0.
DescriptionCVE.org
Improper Input Validation vulnerability in Apache Camel.
This issue affects Apache Camel: through 4.14.7, from 4.15.0 through 4.18.2, from 4.19.0 through 4.20.0.
Users are recommended to upgrade to version 4.14.8, 4.18.3, 4.21.0, which fixes the issue.
AnalysisAI
Improper input validation in Apache Camel - the open-source Java integration framework - affects versions through 4.14.7, 4.15.0 through 4.18.2, and 4.19.0 through 4.20.0, and per the Apache-published advisory carries partial (Low) impact to confidentiality, integrity, and availability. Tagged as an Information Disclosure issue, it is remotely reachable per the CVSS network vector and appears to let a remote attacker submit malformed input that the framework fails to properly validate, potentially exposing limited data or perturbing message processing. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Technical ContextAI
Apache Camel is a widely-used Java-based enterprise integration framework implementing Enterprise Integration Patterns (EIP), routing and mediating messages between systems across hundreds of components/protocols (HTTP, JMS, file, Kafka, etc.). The root cause is CWE-20 (Improper Input Validation): the framework accepts input without adequately verifying that it conforms to expected properties before use, which for an integration engine that parses and transforms external data is a common and impactful class. The single CPE provided (cpe:2.3:a:apache_software_foundation:apache_camel) confirms the core Camel library itself is affected rather than a specific add-on, though the sparse advisory does not name the exact component or endpoint where validation fails.
RemediationAI
Vendor-released patch: upgrade to Apache Camel 4.14.8 (for the 4.14.x and earlier line), 4.18.3 (for the 4.15.0-4.18.2 line), or 4.21.0 (for the 4.19.0-4.20.0 line), matching the fixed release to your current branch as documented in the Apache advisory at https://camel.apache.org/security/CVE-2026-46587.html. Because the advisory does not disclose the vulnerable component or a configuration-level workaround, no reliable feature-toggle mitigation can be stated with confidence; as compensating controls pending upgrade, restrict network exposure of Camel routes that accept untrusted input (for example, place HTTP/consumer endpoints behind authentication or a WAF/reverse proxy and limit source IPs) and validate or sanitize inbound message payloads at the perimeter - noting these are perimeter mitigations that do not fix the underlying library and may not cover all affected code paths. Consult the vendor advisory for any component-specific guidance before relying on a workaround.
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-41865
GHSA-46jf-c9vx-hh79