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 9db698c0f3130428b7caa80a16ae43afb4c935c1 Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Aug 24 11:37:39 2026 +0200 Added CVE-2026-59230 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-59230.md | 21 ++++++++++++++++++++ content/security/CVE-2026-59230.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-59230.md b/content/security/CVE-2026-59230.md new file mode 100644 index 00000000..c8fe1419 --- /dev/null +++ b/content/security/CVE-2026-59230.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-59230" +date: 2026-08-24T10:00:00+02:00 +url: /security/CVE-2026-59230.html +draft: false +type: security-advisory +cve: CVE-2026-59230 +severity: MEDIUM +summary: "Camel-Mail: the MimeMultipart data format copied MIME headers onto the Camel message without a header filter strategy when unmarshalling with headersInline enabled, so a crafted message could inject Camel-internal headers" +description: "The camel-mail component ships a MimeMultipart data format that can unmarshal a MIME multipart message. When it is configured with headersInline set to true, the unmarshal path copies the MIME headers of the incoming message onto the Camel message: it enumerates every header that is not one of the three standard ones it generates itself - Message-ID, MIME-Version and Content-Type - and calls setHeader for each, applying no HeaderFilterStrategy. The names of those MIME heade [...] +mitigation: "Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.4. For deployments that cannot upgrade immediately, leave headersInline at its default of false where the inline headers are not needed, since the copy is only reached when it is enabled. Where it must stay enabled, strip C [...] +credit: "This issue was discovered by Atuin - Automated Vulnerability Discovery Engine, anciety of Tencent Xuanwu Lab" +affected: "From 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0." +fixed: 4.14.9, 4.18.4 and 4.22.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23891 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/24406 (commit ca74898bdef4f2917755ed8911eedfc7f09bd589) and backported to camel-4.14.x in https://github.com/apache/camel/pull/24445 (commit ccdeebc2ae378ba75e5563ddab508fc887527f0c). On camel-4.18.x it landed in two parts: https://github.com/apache/camel/pull/24409 (commit 4d03138dc27c04afdaae6cd40f026c23ed8d7973) followed by https://github.com/apache/camel/pull/24454 (commit cd1333ca1c1d491b4d121878dc025b130554d367), an [...] + +The fix routes the header copy through a HeaderFilterStrategy, so headers in the Camel-internal namespace are matched case-insensitively and skipped rather than set on the message, bringing the data format into line with what the camel-mail consumer already did. The strategy is obtained differently per branch: on main the component relies on the DefaultHeaderFilterStrategy default that already filters Camel-prefixed headers inbound, whereas on camel-4.18.x and camel-4.14.x that default i [...] diff --git a/content/security/CVE-2026-59230.txt.asc b/content/security/CVE-2026-59230.txt.asc new file mode 100644 index 00000000..02c5a37f --- /dev/null +++ b/content/security/CVE-2026-59230.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-59230" +date: 2026-08-24T10:00:00+02:00 +url: /security/CVE-2026-59230.html +draft: false +type: security-advisory +cve: CVE-2026-59230 +severity: MEDIUM +summary: "Camel-Mail: the MimeMultipart data format copied MIME headers onto the Camel message without a header filter strategy when unmarshalling with headersInline enabled, so a crafted message could inject Camel-internal headers" +description: "The camel-mail component ships a MimeMultipart data format that can unmarshal a MIME multipart message. When it is configured with headersInline set to true, the unmarshal path copies the MIME headers of the incoming message onto the Camel message: it enumerates every header that is not one of the three standard ones it generates itself - Message-ID, MIME-Version and Content-Type - and calls setHeader for each, applying no HeaderFilterStrategy. The names of those MIME heade [...] +mitigation: "Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.4. For deployments that cannot upgrade immediately, leave headersInline at its default of false where the inline headers are not needed, since the copy is only reached when it is enabled. Where it must stay enabled, strip C [...] +credit: "This issue was discovered by Atuin - Automated Vulnerability Discovery Engine, anciety of Tencent Xuanwu Lab" +affected: "From 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0." +fixed: 4.14.9, 4.18.4 and 4.22.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23891 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/24406 (commit ca74898bdef4f2917755ed8911eedfc7f09bd589) and backported to camel-4.14.x in https://github.com/apache/camel/pull/24445 (commit ccdeebc2ae378ba75e5563ddab508fc887527f0c). On camel-4.18.x it landed in two parts: https://github.com/apache/camel/pull/24409 (commit 4d03138dc27c04afdaae6cd40f026c23ed8d7973) followed by https://github.com/apache/camel/pull/24454 (commit cd1333ca1c1d491b4d121878dc025b130554d367), an [...] + +The fix routes the header copy through a HeaderFilterStrategy, so headers in the Camel-internal namespace are matched case-insensitively and skipped rather than set on the message, bringing the data format into line with what the camel-mail consumer already did. The strategy is obtained differently per branch: on main the component relies on the DefaultHeaderFilterStrategy default that already filters Camel-prefixed headers inbound, whereas on camel-4.18.x and camel-4.14.x that default i [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqMENsACgkQ406fOAL/ +QQBWLgf+Oj+z+VHrx6yM7Z9e9dNl92PL1gasMVfE8JitfpLJ7F4Fq+KXhDITwUqa +6bZtxHwtiHsjsskCgeDZgtRWIc96xJIOLYcGmdi2AgRkEz4uO7PDGWCKf20je5I4 +flOQ3UBCruZvr63fLxa9BLpIDLE9E3UZ01rbJrBeX3I1q2AMtS5rGMURbooU363K +9PrunaEPnh4eJkjA5WC7GugObTAh1GxEDcvd0KTp6CgzRKDqZrre728hi7oqjj/W +W8gDOqwdJe6A7P2v7YIyQYir/mncR1Jq41AZK85c4ucF9gR3gJ8tUSB7s2L8f33k +LE6xOmGiegIr+FVyWpDzWSpAWOUzDg== +=S+Jh +-----END PGP SIGNATURE-----
