CVE-2026-85247
Apache Camel: Camel-Knative Improper Certificate Validation When SSL Is Enabled Without a Truststore
02 Description
Apache Camel: Camel-Knative Improper Certificate Validation When SSL Is Enabled Without a Truststore
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.42% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 36.3% of scored records. A rank, not a probability.
- NVD base score
- 5.9 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- NVD analysis status
- Awaiting Analysis. NVD last modified this record on 2026-10-19.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-19 10:33Z10 DAYS AGO
- Last updated
- 2026-10-19 17:00Z9 DAYS AGO
- Reserved
- 2026-09-03
- Assigning CNA
- apache
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.9)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- CWE-295Improper Certificate ValidationBase
- Data version
- 5.2
- Document digest
- eaa9b0ce41b7485c63e36335442af910b635aa8c5b2ea64a4b7836bdd2d901e6
05 Affected products
06 References
- camel.apache.orgApache Camel Security Advisory - CVE-2026-85247https://camel.apache.org/security/CVE-2026-85247.html
- issues.apache.orgCAMEL-24443https://issues.apache.org/jira/browse/CAMEL-24443
- github.comFix on main, released in 4.23.0 (commit 26c899d818b8f33732da3678ae00de6af351b622)https://github.com/apache/camel/pull/25824
- github.comBackport to camel-4.22.x, released in 4.22.1 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666)https://github.com/apache/camel/pull/25944
- github.comBackport to camel-4.18.x, released in 4.18.5 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3)https://github.com/apache/camel/pull/25946
07 Remediation
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.