This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit dd95947199ae5b12009795d9cb5bf09b88aa79ff Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:41 2026 +0200 Added CVE-2026-85247 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_013qz9ir11vuQYfQApzwHAHD Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-85247.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85247.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85247.md b/content/security/CVE-2026-85247.md new file mode 100644 index 00000000..499bfd08 --- /dev/null +++ b/content/security/CVE-2026-85247.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85247" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85247.html +draft: false +type: security-advisory +cve: CVE-2026-85247 +severity: MEDIUM +summary: "Camel-Knative: improper certificate validation - enabling SSL without configuring a truststore fell back to trusting every certificate, so turning TLS on was the thing that turned certificate validation off" +description: "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 e [...] +mitigation: "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 remain [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24443 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25824 (commit 26c899d818b8f33732da3678ae00de6af351b622), backported to camel-4.22.x in https://github.com/apache/camel/pull/25944 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) and to camel-4.18.x in https://github.com/apache/camel/pull/25946 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3). + +The issue is classified as CWE-295 Improper Certificate Validation. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. diff --git a/content/security/CVE-2026-85247.txt.asc b/content/security/CVE-2026-85247.txt.asc new file mode 100644 index 00000000..4b1d5db4 --- /dev/null +++ b/content/security/CVE-2026-85247.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85247" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85247.html +draft: false +type: security-advisory +cve: CVE-2026-85247 +severity: MEDIUM +summary: "Camel-Knative: improper certificate validation - enabling SSL without configuring a truststore fell back to trusting every certificate, so turning TLS on was the thing that turned certificate validation off" +description: "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 e [...] +mitigation: "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 remain [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24443 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25824 (commit 26c899d818b8f33732da3678ae00de6af351b622), backported to camel-4.22.x in https://github.com/apache/camel/pull/25944 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) and to camel-4.18.x in https://github.com/apache/camel/pull/25946 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3). + +The issue is classified as CWE-295 Improper Certificate Validation. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqabrUACgkQ406fOAL/ +QQC/pgf/RIzyXAb+oC7R1yFRN4PyJGqf9C3oA9abpwlwGUZppPLEERt30dEXUcRw +k9iWDcVw6KUgcDP3kJU+2gezVrjyt0PYM7vksqcxJisgxNS+S6y6j3F2QRnhgqq3 +K8fseAbHYWZNJVqB+1W3UMU0CRGlxlZWwKjKwWxVTx2yAiD7v/RQvEgaDeqxHXin +AogiQwbMc99Z4zJ/kq59useHyJWy27hxAwzo9bgosWDJtNtL+OfWLM5t0lHJs3Pk +MFv3XTtwW5uOd2de6l8cyu8z50I65+8uECg7fd462xRItCOVbeWb1I+wGmU7X4ZD +wzb04CMqgxxJJvx00zYatxt3maoPjg== +=piQ9 +-----END PGP SIGNATURE-----
