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 5636760174113bee113f03fea1426c94d9d7cdf6 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:43 2026 +0200 Added CVE-2026-85315 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-85315.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85315.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85315.md b/content/security/CVE-2026-85315.md new file mode 100644 index 00000000..ff546321 --- /dev/null +++ b/content/security/CVE-2026-85315.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85315" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85315.html +draft: false +type: security-advisory +cve: CVE-2026-85315 +severity: MEDIUM +summary: "Camel-gRPC: information disclosure - the route exception's message was placed into the gRPC status description, which is transmitted to the caller, so an internal error message reached an external client" +description: "When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is t [...] +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. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onExcept [...] +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-24478 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/25839 (commit 3c99874122e0c4dbad655a1e32bbcaf48cee1e67), backported to camel-4.22.x in https://github.com/apache/camel/pull/25934 (commit 9a6e8222085ed12f73ce76f826aeb69e9d111ff8) and to camel-4.18.x in https://github.com/apache/camel/pull/25935 (commit e6986906e41b3e537d3a5d278525bc09b78b4127). + +The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. 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-85315.txt.asc b/content/security/CVE-2026-85315.txt.asc new file mode 100644 index 00000000..06ef6b51 --- /dev/null +++ b/content/security/CVE-2026-85315.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85315" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85315.html +draft: false +type: security-advisory +cve: CVE-2026-85315 +severity: MEDIUM +summary: "Camel-gRPC: information disclosure - the route exception's message was placed into the gRPC status description, which is transmitted to the caller, so an internal error message reached an external client" +description: "When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is t [...] +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. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onExcept [...] +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-24478 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/25839 (commit 3c99874122e0c4dbad655a1e32bbcaf48cee1e67), backported to camel-4.22.x in https://github.com/apache/camel/pull/25934 (commit 9a6e8222085ed12f73ce76f826aeb69e9d111ff8) and to camel-4.18.x in https://github.com/apache/camel/pull/25935 (commit e6986906e41b3e537d3a5d278525bc09b78b4127). + +The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. 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/QQAFAmqabrYACgkQ406fOAL/ +QQBI6Af/bKxgr0F3BWHisVN9ovUj7vYtTY03xYDPVp/NO+jOepTr6Gu3I7apCauZ +a7Yfn2SdNsTcGpqeeQnC+tdigbPfkizoZyEh/8Q/YJe+b9ILa5dPEe/jmujqtBgp +qKKj/x9dDcVXZEL1/CE/aEWxXmtCIWgPTOGDXy8PDTDJkwkWEsYHVzY/9FlOyqiA +O2P14YvmecCblyc8O2wYWvFk6SqdmCNAgMdNg+Tdo0GIJrL1+MT1Yl35coPbLoSz +hhtuc0golOPI1vud3eRTIm4YaE4xd64uVMDNvYV9lGJmuuutFq/JpUyz8Qy0P5xE +ehGL6yuYu/pE4icQVrJBoBZ2eynfeA== +=bBKU +-----END PGP SIGNATURE-----
