oscerd opened a new pull request, #1686: URL: https://github.com/apache/camel-website/pull/1686
## Summary Adds new Apache Camel security advisories under `content/security/`, prepared for the **2026-07-03** release. Each advisory is a Hugo page (`CVE-XXXX.md`) plus a PGP-clearsigned copy (`CVE-XXXX.txt.asc`) signed with the Camel security key (`27663406EB6DBAF5291F2615E34E9F3802FF4100`, SHA-512). Only `content/security/` is touched. ## Advisories (29) CVE-2026-40047, CVE-2026-40859, CVE-2026-42527, CVE-2026-43865, CVE-2026-46453, CVE-2026-46454, CVE-2026-46455, CVE-2026-46456, CVE-2026-46457, CVE-2026-46584, CVE-2026-46585, CVE-2026-46590, CVE-2026-46591, CVE-2026-46592, CVE-2026-46726, CVE-2026-48203, CVE-2026-48204, CVE-2026-48205, CVE-2026-48206, CVE-2026-49086, CVE-2026-49097, CVE-2026-49098, CVE-2026-49099, CVE-2026-49365, CVE-2026-53913, CVE-2026-55993, CVE-2026-55994, CVE-2026-56139, CVE-2026-56140 ## Notable structure Several advisories were scoped so each targets a single component, with bidirectional cross-references: - **camel-vertx-websocket** — `CVE-2026-46726`; siblings `CVE-2026-55993` (camel-atmosphere-websocket) and `CVE-2026-55994` (camel-iggy). Shared fix: CAMEL-23532. - **camel-netty-http** — `CVE-2026-49365`; sibling `CVE-2026-56139` (camel-undertow). Shared fix: CAMEL-23651. - **camel-aws2-sqs** — `CVE-2026-46456`; sibling `CVE-2026-56140` (camel-aws2-sns — `LOW`, defense-in-depth: aws2-sns is producer-only, so no reachable inbound path). Shared fix: CAMEL-23506. ## Notes - Advisory `date` fields are set to `2026-07-03`, except `CVE-2026-42527` which retains its earlier `2026-04-29` date. - The security section list is rendered automatically by the Hugo template, so no index/data file changes are needed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
