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 c354d83d8233b0b37fbf5f2ad0fb0b0732403e28 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85296 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-85296.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85296.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85296.md b/content/security/CVE-2026-85296.md new file mode 100644 index 00000000..6d47daa2 --- /dev/null +++ b/content/security/CVE-2026-85296.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85296" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85296.html +draft: false +type: security-advisory +cve: CVE-2026-85296 +severity: MEDIUM +summary: "Camel-AS2: cross-partner signing key confusion - per-request signing material was held in state shared across requests, so a receipt could be signed with the key belonging to a different trading partner" +description: "Signing material belonging to an individual request was stored in state that is shared across requests rather than confined to the request being processed. Where a deployment serves more than one trading partner, concurrent or successive requests could therefore observe each other's material, and a Message Disposition Notification could be signed with the key of a partner other than the one the receipt was for. The result is cross-partner key confusion: a receipt attributab [...] +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. Per-request signing keys are now confined to the request being processed in ResponseMDN. For deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them." +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-24429 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/25641 (commit 659176dec58522fbebea11a1f6d5ee5c37f235d9), backported to camel-4.22.x in https://github.com/apache/camel/pull/25869 (commit ab5eacd3fa485eb990cf021dc56e48465c060d39) and to camel-4.18.x in https://github.com/apache/camel/pull/25870 (commit 19f91785f9e975e7734efd514946c2dfdbdbd1d7). + +The issue is classified as CWE-488 Exposure of Data Element to Wrong Session. 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-85296.txt.asc b/content/security/CVE-2026-85296.txt.asc new file mode 100644 index 00000000..e522f58f --- /dev/null +++ b/content/security/CVE-2026-85296.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85296" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85296.html +draft: false +type: security-advisory +cve: CVE-2026-85296 +severity: MEDIUM +summary: "Camel-AS2: cross-partner signing key confusion - per-request signing material was held in state shared across requests, so a receipt could be signed with the key belonging to a different trading partner" +description: "Signing material belonging to an individual request was stored in state that is shared across requests rather than confined to the request being processed. Where a deployment serves more than one trading partner, concurrent or successive requests could therefore observe each other's material, and a Message Disposition Notification could be signed with the key of a partner other than the one the receipt was for. The result is cross-partner key confusion: a receipt attributab [...] +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. Per-request signing keys are now confined to the request being processed in ResponseMDN. For deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them." +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-24429 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/25641 (commit 659176dec58522fbebea11a1f6d5ee5c37f235d9), backported to camel-4.22.x in https://github.com/apache/camel/pull/25869 (commit ab5eacd3fa485eb990cf021dc56e48465c060d39) and to camel-4.18.x in https://github.com/apache/camel/pull/25870 (commit 19f91785f9e975e7734efd514946c2dfdbdbd1d7). + +The issue is classified as CWE-488 Exposure of Data Element to Wrong Session. 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/ +QQDXewf/aoyxF5Z1jooYzrjYGlfdHq3F6K/LsCQV1SuRffkdmLGtTaMOyKsZs+4t +ziqnY3sZ4/yqKTzr6lzA3yOZuWHjeRwnZptXQVEnTMjhhUj2ORMTAQDFzHTyxDlr +u7AZTgaT6IXOmFkNwhNqBGLPDnEBRapuSjlfQxHJHGnQxT1BGdGUA4swM2r7OWve +Zaqp7Z1QFREn7SmHg3RnEpVzNfrLZunsjXguq7E3tqsEMEUITii0ltCBaamlGHG4 +PPh00Va7oN4eWsCUPaajEvBLYZMkLSxsgsegig1mL4OdQVjLdE62uIByklGd1HOH +WtAQVbt4eu2VnXASAPgrOvvd+rWIjg== +=bxLy +-----END PGP SIGNATURE-----
