(camel-website) branch quick-fix/security-report-email updated: chore: use security@apache.org in security advisory blog posts

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch quick-fix/security-report-email
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/quick-fix/security-report-email by this push:
     new 92847134 chore: use security@apache.org in security advisory blog posts
92847134 is described below

commit 928471342184850d464023f1706c527d3175f64a
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Oct 16 16:49:16 2026 +0200

    chore: use security@apache.org in security advisory blog posts
    
    Apache Camel has no security@camel.apache.org list; vulnerabilities
    are reported to the ASF Security Team at security@apache.org.
    
    Co-Authored-By: Claude Opus 5.5 (1M context) <no...@anthropic.com>
---
 content/blog/2026/07/camel-security-advisories-4.21.0/index.md | 4 ++--
 content/blog/2026/10/camel-security-advisories-4.23.0/index.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/blog/2026/07/camel-security-advisories-4.21.0/index.md b/content/blog/2026/07/camel-security-advisories-4.21.0/index.md
index dc1291ff..b0657986 100644
--- a/content/blog/2026/07/camel-security-advisories-4.21.0/index.md
+++ b/content/blog/2026/07/camel-security-advisories-4.21.0/index.md
@@ -221,7 +221,7 @@ work is the reason the header family turned up in twenty-two components rather t
 methodical sweep across the component set, not a one-off report, and it saved us a lot of time.
 
 Everyone here is named in the advisory they reported. If you find something, mail
-[security@camel.apache.org](mailto:security@camel.apache.org) privately, and see the
+[security@apache.org](mailto:security@apache.org) privately, and see the
 [ASF security policy](https://www.apache.org/security/) for how the process works.
 
 ## The full batch
@@ -293,4 +293,4 @@ the one with no exploit path at all. We would rather have those on the record th
 
 *Release dates and advisory data in this post come from the published
 [Apache Camel release announcements](/blog/) and [security advisories](/security/). Report
-vulnerabilities privately to [security@camel.apache.org](mailto:security@camel.apache.org).*
+vulnerabilities privately to [security@apache.org](mailto:security@apache.org).*
diff --git a/content/blog/2026/10/camel-security-advisories-4.23.0/index.md b/content/blog/2026/10/camel-security-advisories-4.23.0/index.md
index 962c0b09..169c86e6 100644
--- a/content/blog/2026/10/camel-security-advisories-4.23.0/index.md
+++ b/content/blog/2026/10/camel-security-advisories-4.23.0/index.md
@@ -89,7 +89,7 @@ other ten were reported by:
 Thank you to all of them.
 
 If you find a security issue in Apache Camel, please report it privately to
-[security@camel.apache.org](mailto:security@camel.apache.org). The [ASF security policy](https://www.apache.org/security/)
+[security@apache.org](mailto:security@apache.org). The [ASF security policy](https://www.apache.org/security/)
 describes how the process works.
 
 ## Learn more