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 3966af48c0878ce24fdcaec087eba3c83bd586f6 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85314 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-85314.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85314.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85314.md b/content/security/CVE-2026-85314.md new file mode 100644 index 00000000..bdd141be --- /dev/null +++ b/content/security/CVE-2026-85314.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85314" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85314.html +draft: false +type: security-advisory +cve: CVE-2026-85314 +severity: MEDIUM +summary: "Camel-Mail: header injection - the MimeMultipart data format mapped mail.smtp headers onto the Exchange without applying the filter, leaving open the path that CVE-2026-46584 was intended to close" +description: "CVE-2026-46584 addressed mail headers reaching the Exchange without passing through a header filter, but the MimeMultipart data format retained an unfiltered path: unmarshalling a multipart message mapped mail.smtp headers onto the Exchange with no filter applied. Those names sit outside the Camel namespace that consumer filters block, so a message crafted by an external sender could still set them, and the mail.smtp namespace influences how a downstream mail producer conne [...] +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 MimeMultipart data format now applies the header filter on unmarshal, closing the path CVE-2026-46584 left open. For deployments that cannot upgrade immediately, strip the namespace after the data format with removeHeaders(\"mail.smtp*\") before any mail producer." +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-24419 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/25568 (commit c2bcb24814a806ced928e612ce5da1a6e3658234), backported to camel-4.22.x in https://github.com/apache/camel/pull/25765 (commit 451d3037ee60544cb2158675959416fec5cc5745) and to camel-4.18.x in https://github.com/apache/camel/pull/25766 (commit e25a496381c1330aea16f26136ce02bb818ccccb). + +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-85314.txt.asc b/content/security/CVE-2026-85314.txt.asc new file mode 100644 index 00000000..1e01f70b --- /dev/null +++ b/content/security/CVE-2026-85314.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85314" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85314.html +draft: false +type: security-advisory +cve: CVE-2026-85314 +severity: MEDIUM +summary: "Camel-Mail: header injection - the MimeMultipart data format mapped mail.smtp headers onto the Exchange without applying the filter, leaving open the path that CVE-2026-46584 was intended to close" +description: "CVE-2026-46584 addressed mail headers reaching the Exchange without passing through a header filter, but the MimeMultipart data format retained an unfiltered path: unmarshalling a multipart message mapped mail.smtp headers onto the Exchange with no filter applied. Those names sit outside the Camel namespace that consumer filters block, so a message crafted by an external sender could still set them, and the mail.smtp namespace influences how a downstream mail producer conne [...] +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 MimeMultipart data format now applies the header filter on unmarshal, closing the path CVE-2026-46584 left open. For deployments that cannot upgrade immediately, strip the namespace after the data format with removeHeaders(\"mail.smtp*\") before any mail producer." +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-24419 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/25568 (commit c2bcb24814a806ced928e612ce5da1a6e3658234), backported to camel-4.22.x in https://github.com/apache/camel/pull/25765 (commit 451d3037ee60544cb2158675959416fec5cc5745) and to camel-4.18.x in https://github.com/apache/camel/pull/25766 (commit e25a496381c1330aea16f26136ce02bb818ccccb). + +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/ +QQC8Dgf/ewFaHavt/oO+Nr7tioVZ9+Hkvdf2306apEi1tTy0HxeT5N0s+7fTudyv +Rf83vDB/PQWwI3RnGFYvSLYMcSwe99NFSqrker8smPonGeIJOAbTZmmS9V4Sd94H +xZjFzfO9v/g/mm+lTqU0BA9xCvTwEzY/zg6MhvxDLLzPjpuAQjAENL+jC9CqtYpS +Vowaldlha+4X3nADqTeZgodIo3Rtjzj1ObybluKq9k80QtjX0Zr3qLplOFKvrfWw +onH+I7t8PFU6iYcwScawmiGTP49H3b2P0DMmoyCNs8QkukDBBLQ1sw+/qCsdV7aP +b1Ze39m2OwekLBO4joMqSF5kccSTZA== +=qozL +-----END PGP SIGNATURE-----
