Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85247 Overview
CVE-2026-85247 is an Improper Certificate Validation flaw [CWE-295] in the Apache Camel Knative component. When Secure Sockets Layer (SSL) is enabled on the Knative HTTP client without an explicit truststore, the client falls back to trusting every presented certificate instead of using the Java Virtual Machine (JVM) default trust anchors. Deployments that enable TLS without configuring a truststore therefore establish encrypted connections with no peer authentication. An attacker positioned on the network path can terminate the connection, read traffic, and impersonate the Knative endpoint.
Critical Impact
Enabling TLS on the Camel Knative HTTP client without a truststore silently disables certificate validation, exposing traffic to machine-in-the-middle interception.
Affected Products
- Apache Camel from 4.0.0 before 4.18.5
- Apache Camel from 4.19.0 before 4.22.1
- Apache Camel Knative component
Discovery Timeline
- 2026-10-19 - CVE-2026-85247 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-85247
Vulnerability Analysis
The defect lives in the Knative HTTP client configuration path inside Apache Camel. When a user turns SSL on but does not supply a truststore, the client options are populated with a trust-all strategy rather than left unset. The resulting Transport Layer Security (TLS) handshake accepts any X.509 certificate chain, including attacker-controlled ones. Confidentiality guarantees collapse because the client cannot distinguish the real Knative broker from an interception proxy.
The issue is a framework default problem rather than a misconfiguration by the operator. Turning encryption on should not be the action that turns authentication off. Because the dangerous state is reached by omission, deployments that followed the documented path to enable TLS can inherit the flaw without any explicit opt-in to insecure trust.
Root Cause
The Knative HTTP client builder treated the absence of a truststore as a signal to trust all peers. The expected behavior across the rest of Camel, including SSLContextParameters, is to leave trust options unset so the JVM default trust anchors apply. The deviation in the Knative component created a certificate validation bypass whenever the trust.all property was not explicitly disabled.
Attack Vector
Exploitation requires an attacker with a network position between the Camel Knative client and its target endpoint. The adversary presents a certificate for the destination hostname signed by any issuer, including a self-generated certificate authority. The Camel client completes the handshake, encrypts traffic to the attacker, and the attacker proxies traffic to the real endpoint. The attacker reads and can modify the plaintext in transit, including routed event payloads and headers.
See the Apache Camel CVE-2026-85247 Advisory and the fixing changes in GitHub Pull Request #25824, GitHub Pull Request #25944, and GitHub Pull Request #25946 for the implementation details.
Detection Methods for CVE-2026-85247
Indicators of Compromise
- TLS sessions from Camel Knative clients negotiating with certificates issued by unexpected or unknown certificate authorities.
- Camel runtime configurations with SSL enabled on the Knative component but no truststore or SSLContextParameters reference defined.
- Routes resolving Knative endpoints to IP addresses or hostnames that differ from the deployed Knative broker or service.
Detection Strategies
- Inventory running Apache Camel instances and flag any version in the ranges 4.0.0 to 4.18.4 and 4.19.0 to 4.22.0 that load the camel-knative component.
- Scan Camel configuration sources, including YAML, XML, and Java DSL, for Knative client definitions where TLS is enabled without a truststore property.
- Capture TLS handshake metadata at the egress gateway and alert when a Camel workload accepts a certificate chain that does not terminate at a known internal or public root.
Monitoring Recommendations
- Log the resolved SSL parameters at Camel startup and compare them to a baseline that requires an explicit truststore reference for the Knative component.
- Monitor Knative broker certificate fingerprints from client-side telemetry and alert on fingerprint changes that are not tied to a planned rotation.
- Centralize Camel application logs and TLS negotiation events in a security data platform to correlate configuration drift with anomalous handshake outcomes.
How to Mitigate CVE-2026-85247
Immediate Actions Required
- Upgrade Apache Camel to 4.23.0, 4.22.1 on the 4.22.x LTS stream, or 4.18.5 on the 4.18.x LTS stream.
- For every Camel route using the Knative component with SSL enabled, configure a truststore explicitly before the next deployment cycle.
- Audit production routes for any reliance on the implicit trust-all behavior and remediate before upgrading, since the fix changes default trust to the JVM anchors.
Patch Information
The fix ships in Apache Camel 4.23.0 and in the LTS releases 4.22.1 and 4.18.5. After the upgrade, if no truststore is configured, trust options are left unset and the JVM default trust anchors apply, matching the behavior of SSLContextParameters elsewhere in Camel. Trust-all is now only reached by explicitly setting the trust.all property, which remains available for development against clusters with self-signed certificates. Review the Apache CAMEL-24443 JIRA Issue for the full change record.
Workarounds
- If an immediate upgrade is not possible, configure a truststore wherever SSL is enabled on the Knative HTTP client so trust falls back to a defined set of anchors.
- Terminate TLS at a service mesh sidecar or trusted egress proxy that performs certificate validation on behalf of the Camel workload.
- Restrict Camel Knative client egress to a known broker address or service mesh identity to reduce the window for machine-in-the-middle positioning.
# Configuration example: enable SSL on the Camel Knative component with an explicit truststore
camel.component.knative.ssl=true
camel.component.knative.truststore=/etc/camel/truststore.jks
camel.component.knative.truststore-password=${TRUSTSTORE_PASSWORD}
# Do NOT set the following unless intentionally trusting all certificates in a dev cluster
# camel.component.knative.trust.all=true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

