CVE-2026-85247: Apache Camel: Camel-Knative Improper Certificate Validation When SSL Is Enabled Without a Truststore

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.4%

Up from 0.3% on 22 Oct 2026.

EPSS score, percentile 36.6 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

5.9 Medium

CVSS v3.1 base score, given by the CNA

What should I do?

Upgrade to Apache Camel 4.23.0, which fixes the issue. Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (4)

Which versions are affected?

Affected

• from 4.0.0 to before 4.18.5
• from 4.19.0 to before 4.22.1

Unaffected 4.18.5; 4.22.1; 4.23.0

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Solution (from the CVE record)

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.

Workaround (from the CVE record)

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.

Advisories and patches

• Fix on main, released in 4.23.0 (commit 26c899d818b8f33732da3678ae00de6af351b622) (Patch)
• Backport to camel-4.22.x, released in 4.22.1 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) (Patch)
• Backport to camel-4.18.x, released in 4.18.5 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3) (Patch)
• Apache Camel Security Advisory - CVE-2026-85247 (Vendor advisory)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Versions not listed are: unaffected.

Versions the record lists as unaffected: 4.18.5, 4.22.1, 4.23.0.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

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…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2026-85247 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 19 Oct 2026.
• The CVE record carries a CVSS v3.1 base score of 5.9 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.4% (percentile 36.6), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact partial.
• The credits in the CVE record name Anthropic (Claude) as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

Apache Camel: Camel-Knative Improper Certificate Validation When SSL Is Enabled Without a Truststore

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.

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline

Known exploited Apache vulnerabilities

• CVE-2016-3081: Apache Struts Command Injection Vulnerability (added 8 Oct 2026)
• CVE-2026-34486: Apache Tomcat Missing Encryption of Sensitive Data Vulnerability (added 4 Aug 2026)
• CVE-2026-34197: Apache ActiveMQ Improper Input Validation Vulnerability (added 16 Apr 2026)
• CVE-2024-38475: Apache HTTP Server Improper Escaping of Output Vulnerability (added 1 May 2025)
• CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability (added 1 Apr 2025)