This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch new-wave-of-cves in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit b33477d85c440b8ddbb0651fdd43c6e847e80e77 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85312 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-85312.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85312.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85312.md b/content/security/CVE-2026-85312.md new file mode 100644 index 00000000..438db24a --- /dev/null +++ b/content/security/CVE-2026-85312.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85312" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85312.html +draft: false +type: security-advisory +cve: CVE-2026-85312 +severity: MEDIUM +summary: "Camel-Core: saga hijacking - the saga processor consulted a Long-Running-Action header that sits outside the filtered Camel namespace, so an external sender could name the saga an exchange joined" +description: "The saga processor consulted a header named Long-Running-Action to decide which saga an exchange belonged to. The name carries no Camel prefix, so it sits outside the namespace that consumer header filters block, and an external sender could supply it on an inbound message. That let the sender name the saga the exchange joined, attaching their request to a long-running action started by someone else, or causing compensation to be associated with an action they did not initi [...] +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. The header is now consulted only for a saga service that actually uses it, rather than on every exchange. For deployments that cannot upgrade immediately, strip the header at the trust boundary with removeHeaders(\"Long-Running-Action\") on every consumer that accepts messages from an untrus [...] +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-24449 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/25828 (commit dfde003151a0753f997f9eea7d071097f4b00db2), backported to camel-4.22.x in https://github.com/apache/camel/pull/25940 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25942 (commit af1efbcccf5882b1ef0094db718972da3190e7e9). + +The issue is classified as CWE-20 Improper Input 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-85312.txt.asc b/content/security/CVE-2026-85312.txt.asc new file mode 100644 index 00000000..4fe9c196 --- /dev/null +++ b/content/security/CVE-2026-85312.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85312" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85312.html +draft: false +type: security-advisory +cve: CVE-2026-85312 +severity: MEDIUM +summary: "Camel-Core: saga hijacking - the saga processor consulted a Long-Running-Action header that sits outside the filtered Camel namespace, so an external sender could name the saga an exchange joined" +description: "The saga processor consulted a header named Long-Running-Action to decide which saga an exchange belonged to. The name carries no Camel prefix, so it sits outside the namespace that consumer header filters block, and an external sender could supply it on an inbound message. That let the sender name the saga the exchange joined, attaching their request to a long-running action started by someone else, or causing compensation to be associated with an action they did not initi [...] +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. The header is now consulted only for a saga service that actually uses it, rather than on every exchange. For deployments that cannot upgrade immediately, strip the header at the trust boundary with removeHeaders(\"Long-Running-Action\") on every consumer that accepts messages from an untrus [...] +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-24449 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/25828 (commit dfde003151a0753f997f9eea7d071097f4b00db2), backported to camel-4.22.x in https://github.com/apache/camel/pull/25940 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25942 (commit af1efbcccf5882b1ef0094db718972da3190e7e9). + +The issue is classified as CWE-20 Improper Input 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/QQAFAmqabrYACgkQ406fOAL/ +QQCCFAf/TJghcb+dX5z/9GLh2Z+uGScAA0OzBphOsioKsWwQ6Cjr8sMMTLpmyOkR +XLy5cu7OXTzZcwnEiFet09RKOlNdD9R0T1RMPZIQEOXqUlSQBwerbv+I3oy8IW8s +2IWpRMWqTl309a3KQAAzV13CbterTYHylS7vE06pCvDt28GrKhl2nJEnJTWIRcam +10kszKhw4cCZu6ucv5z/gdmaDHaXqvsjSmczmUotBjD9O5DT71WP3oySqkBWlNTW +Kv9DYnavt7R2yU18bPkyQ5oseQn+7nlUutVxhEzntafUf72CVK6fuW/bh2XAPVg6 +hmNj4WcrGiQ3u2YCKl66sHXxOVCIEQ== +=sykJ +-----END PGP SIGNATURE-----
