CVE-2026-85247

Improper Certificate Validation vulnerability in Apache Camel Knative component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When SSL was enabled on the Knative HTTP client but no truststore was configured, the client options fell back to trusting every presented certificate rather than to the JVM's default trust anchors. A deployment that switched TLS on without also configuring a truststore therefore obtained an encrypted connection with no peer authentication, which an attacker positioned on the network path can terminate and read. The dangerous state is reached by omission rather than by an explicit opt-in, which is what makes it a framework defect: turning TLS on should not be the thing that turns certificate validation off. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. With no truststore configured the trust options are now left unset so the JVM default trust anchors apply, the same fallback SSLContextParameters and the rest of Camel use. Trusting every certificate is now reached only by asking for it explicitly through the trust.all property, which remains available for development against a cluster with a self-signed certificate. For deployments that cannot upgrade immediately, configure a truststore explicitly wherever SSL is enabled. After upgrading, a deployment that was relying on the implicit trust-all behaviour must either configure a truststore or set the trust.all property deliberately.

• CWE-295

• https://camel.apache.org/security/CVE-2026-85247.htmlMitigation, Patch, Vendor Advisory
• https://github.com/apache/camel/pull/25824Issue Tracking, Patch
• https://github.com/apache/camel/pull/25944Issue Tracking, Patch
• https://github.com/apache/camel/pull/25946Issue Tracking, Patch
• https://issues.apache.org/jira/browse/CAMEL-24443Issue Tracking, Patch, Vendor Advisory

Published

Oct 19, 2026

Last Modified

Nov 3, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-8524Out of bounds write in WebAudio in Google Chrome prior to 14…8.8
• CVE-2026-85241A weakness has been identified in SpecterOps BloodHound up t…6.3
• CVE-2026-85242PlaywrightCapture contains a server-side request forgery (SS…6.9
• CVE-2026-85243Improper Validation of Integrity Check Value vulnerability i…5.9
• CVE-2026-85245Exposure of Data Element to Wrong Session vulnerability in A…5.9
• CVE-2026-85246Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-85248Concurrent Execution using Shared Resource with Improper Syn…5.9
• CVE-2026-85249Improper Input Validation vulnerability in Apache Camel Tika…6.5
• CVE-2026-8525Heap buffer overflow in ANGLE in Google Chrome on Mac prior …8.3
• CVE-2026-85250Improper Restriction of XML External Entity Reference vulner…7.5
• CVE-2026-85251Exposure of Sensitive Information to an Unauthorized Actor v…7.5
• CVE-2026-85254Improper Handling of Case Sensitivity vulnerability in Apach…6.5