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 8867f6b78d0befccc3061a6086f68bf545d7b476
Author: Andrea Cosentino <[email protected]>
AuthorDate: Mon Oct 12 14:52:16 2026 +0200

    Remove a stale sentence from CVE-2026-78162 and re-sign it
    
    When the affected range was widened to start at 4.0.0, the closing
    paragraph kept "The affected ranges above therefore start at the two
    supported streams.", which no longer holds. The sentence is dropped; the
    rest of the paragraph already says those lines reached end of life and
    will not receive a fix.
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
    Signed-off-by: Andrea Cosentino <[email protected]>
---
 content/security/CVE-2026-78162.md      |  2 +-
 content/security/CVE-2026-78162.txt.asc | 18 +++++++++---------
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/content/security/CVE-2026-78162.md 
b/content/security/CVE-2026-78162.md
index d2592188..4292dbda 100644
--- a/content/security/CVE-2026-78162.md
+++ b/content/security/CVE-2026-78162.md
@@ -20,4 +20,4 @@ CAMEL-24413 covers ReplicatedHazelcastAggregationRepository 
and was merged on ma
 
 This advisory is an incomplete-fix follow-on to CVE-2026-43865 (CAMEL-23414), 
which introduced HazelcastSerializationFilterHelper and applied the default 
filter to four of the six Camel-built configuration sites. The two sites 
described above were not covered by that change, so deployments that upgraded 
to 4.14.8, 4.18.3 or 4.21.0 in response to that advisory remained exposed 
through them. This issue is distinct from the Hazelcast library deserialization 
advisories CVE-2016-10750 and CVE [...]
 
-Releases from 4.0.0 through the 4.14.x line are affected as well, since 
ReplicatedHazelcastAggregationRepository has carried the defect since it was 
introduced, but those release lines reached end of life before this issue was 
resolved and no fix will be issued for them. The affected ranges above 
therefore start at the two supported streams.
+Releases from 4.0.0 through the 4.14.x line are affected as well, since 
ReplicatedHazelcastAggregationRepository has carried the defect since it was 
introduced, but those release lines reached end of life before this issue was 
resolved and no fix will be issued for them.
diff --git a/content/security/CVE-2026-78162.txt.asc 
b/content/security/CVE-2026-78162.txt.asc
index fab47851..2d7af6f7 100644
--- a/content/security/CVE-2026-78162.txt.asc
+++ b/content/security/CVE-2026-78162.txt.asc
@@ -23,15 +23,15 @@ CAMEL-24413 covers ReplicatedHazelcastAggregationRepository 
and was merged on ma
 
 This advisory is an incomplete-fix follow-on to CVE-2026-43865 (CAMEL-23414), 
which introduced HazelcastSerializationFilterHelper and applied the default 
filter to four of the six Camel-built configuration sites. The two sites 
described above were not covered by that change, so deployments that upgraded 
to 4.14.8, 4.18.3 or 4.21.0 in response to that advisory remained exposed 
through them. This issue is distinct from the Hazelcast library deserialization 
advisories CVE-2016-10750 and CVE [...]
 
-Releases from 4.0.0 through the 4.14.x line are affected as well, since 
ReplicatedHazelcastAggregationRepository has carried the defect since it was 
introduced, but those release lines reached end of life before this issue was 
resolved and no fix will be issued for them. The affected ranges above 
therefore start at the two supported streams.
+Releases from 4.0.0 through the 4.14.x line are affected as well, since 
ReplicatedHazelcastAggregationRepository has carried the defect since it was 
introduced, but those release lines reached end of life before this issue was 
resolved and no fix will be issued for them.
 -----BEGIN PGP SIGNATURE-----
 
-iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqe0foACgkQ406fOAL/
-QQDPCAgAtasbi1FY/eSRh3orKToijpxfLQwJ3W16AOjqwslpG2rUdYlfHghJ+TRa
-hVQcTkikDa4W4EugI8uLJdtSF3iPhh04d1SOz+LuBwBn5WMDA0nKb2cAJIqZ9jS1
-QLji49H8N3dFPY9A0Zr+IUyGSu4QaCfIEfQEu2+NtmGZ52nYpSexC94RbVJjJy++
-Fu7IUdnYL+VKtYpHiB7iixbsgU0z8NWj1Hyf7RwYFCT0rN68hiKtIk0rs/20R1F0
-XUgxOA02IPfdVe58hoSiRZdi2jrkfZBjeddK8GywAwgHQtPumSPS5L1EV53TD3rw
-5KrCCoW1sISN0WUyJPR85VRZYrBVYg==
-=AhaJ
+iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrM1+EACgkQ406fOAL/
+QQCXnQf/eIzueh+vQqg3/KlfYQxQBdAQTQ0T9yutOlqfB720DCPesJ2y8mOjo0XL
+CSbcjjf1dtEgqc7vPVkrLal2p68FPg/bL0fXQopiY/qMf9G7JZgaQKBjIPFHzk+C
+EQDOh+0PBuaFYwSBIM9ggyPZ90kMcOq7HQq8wxbUI0w/X0jKyAc2ysR+KOd852ab
+JQg/yUJQ+FX9dZFiEFfLix7CEHuIsMtUC2UoZ89/m6SuwjfcAQNzfJdki3OGR+yz
+3yFuwhG/y8qUW2SJgIrwGP6m+W8+mpqxrdpRgtk5BovGRK5HtTPtEKiAnS+CUE1s
+qIDau9TXZPktGcsFMiPjozSTvf4Jog==
+=2NYs
 -----END PGP SIGNATURE-----

Reply via email to