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 cdcc129cbf4d312752864e69017747f0bb9297fb Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Jun 15 12:27:05 2026 +0200 Added CVE-2026-43865 Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-43865.md | 17 +++++++++++++++++ content/security/CVE-2026-43865.txt.asc | 31 +++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) diff --git a/content/security/CVE-2026-43865.md b/content/security/CVE-2026-43865.md new file mode 100644 index 00000000..e379a29e --- /dev/null +++ b/content/security/CVE-2026-43865.md @@ -0,0 +1,17 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-43865" +date: 2026-06-09T10:00:00+02:00 +url: /security/CVE-2026-43865.html +draft: false +type: security-advisory +cve: CVE-2026-43865 +severity: MEDIUM +summary: "Apache Camel: Camel-Hazelcast: Unsafe Java deserialization in default-configured managed Hazelcast instances enables remote code execution" +description: "The camel-hazelcast component creates and manages Hazelcast instances using a default configuration that applies no Java deserialization filter. When Camel builds the Hazelcast Config itself - that is, when no user-supplied HazelcastInstance, hazelcastConfigUri, or referenced Config bean is provided - neither Hazelcast's JavaSerializationFilterConfig nor a Camel-side ObjectInputFilter is configured, so objects received over the Hazelcast cluster protocol are deserialized in [...] +mitigation: "Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes Camel apply a default Hazelcast JavaSerializationFilterConfig (whitelisting the java., javax. and org.apache.camel. class-name prefixes and blacklisting java.net.) to instances it creates from its own defau [...] +credit: "This issue was discovered by gaorenyusi" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23414 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/22943 (commit 7a309042f22493082647a410d9d8cafd672b1c74) and backported to camel-4.18.x (commit 5caf4368551f6d3b61690d5db03869491390d446) and camel-4.14.x (commit 974a11b5ed5e2d50722f33aa48f61898395ea45b). This issue is distinct from the Hazelcast library deserialization advisorie [...] diff --git a/content/security/CVE-2026-43865.txt.asc b/content/security/CVE-2026-43865.txt.asc new file mode 100644 index 00000000..850b811d --- /dev/null +++ b/content/security/CVE-2026-43865.txt.asc @@ -0,0 +1,31 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-43865" +date: 2026-06-09T10:00:00+02:00 +url: /security/CVE-2026-43865.html +draft: false +type: security-advisory +cve: CVE-2026-43865 +severity: MEDIUM +summary: "Apache Camel: Camel-Hazelcast: Unsafe Java deserialization in default-configured managed Hazelcast instances enables remote code execution" +description: "The camel-hazelcast component creates and manages Hazelcast instances using a default configuration that applies no Java deserialization filter. When Camel builds the Hazelcast Config itself - that is, when no user-supplied HazelcastInstance, hazelcastConfigUri, or referenced Config bean is provided - neither Hazelcast's JavaSerializationFilterConfig nor a Camel-side ObjectInputFilter is configured, so objects received over the Hazelcast cluster protocol are deserialized in [...] +mitigation: "Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes Camel apply a default Hazelcast JavaSerializationFilterConfig (whitelisting the java., javax. and org.apache.camel. class-name prefixes and blacklisting java.net.) to instances it creates from its own defau [...] +credit: "This issue was discovered by gaorenyusi" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23414 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/22943 (commit 7a309042f22493082647a410d9d8cafd672b1c74) and backported to camel-4.18.x (commit 5caf4368551f6d3b61690d5db03869491390d446) and camel-4.14.x (commit 974a11b5ed5e2d50722f33aa48f61898395ea45b). This issue is distinct from the Hazelcast library deserialization advisorie [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmovy8AACgkQ406fOAL/ +QQD7JAf/YgC+G4HXeCYgWMqvG1pTCU0Ql0U+lwH96AwFBlAaK/mIl7oVER9+/AqY +LI7LU52ZQ9e9rv8tFhRc6F6DyRXtLx2rXG4zmPiq+ResF4X8unYUDQgXSYdgp1AN +Qvygd6toAQs1/i1Ox1RAeU+/+qS6RxEvWf/rbvQxjeEWZVyMnmHCt5EO9KPL4PRA +RxSnKiyXGERdSga1XnesUQgtolAyLk/OAth0CJjVzuAUTAHdHmC0ZOhGApIM5lkS +uyzogTHlMS0LXLYkghIhmsyRbnUaJSZsuL1NsOA3gyPEzaXsiXKWEAw7JWo1jAoS +S4ytZVtWnX5veJNAJub41Ni61XoxOg== +=y0Ru +-----END PGP SIGNATURE-----
