From b031feef060f12ec9190b9df171b7209add8345c Mon Sep 17 00:00:00 2001 From: Hongsheng Liu Date: Thu, 13 Aug 2026 16:33:09 +0800 Subject: [PATCH] [Doc] Clarify private security contact guidance Signed-off-by: Hongsheng Liu --- docs/community/contact_us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/community/contact_us.md b/docs/community/contact_us.md index eccb0c086..cae175f4c 100644 --- a/docs/community/contact_us.md +++ b/docs/community/contact_us.md @@ -6,4 +6,4 @@ ## Security Disclosures -Do not report suspected security vulnerabilities in public GitHub issues, pull requests, discussions, or Slack channels. To arrange a private report, send a direct message to one of the [lead maintainers](governance.md#lead-maintainers) in [vLLM Slack](https://slack.vllm.ai/). If you cannot send a direct message, post only a detail-free request in `sig-omni` asking a lead maintainer to contact you. +Do not share vulnerability details in public GitHub issues, pull requests, discussions, or Slack channels. To arrange a private report, send a direct message to one of the [lead maintainers](governance.md#lead-maintainers) in [vLLM Slack](https://slack.vllm.ai/). If you cannot send a direct message, you may post a detail-free request in `sig-omni` asking a lead maintainer to contact you privately; do not include any vulnerability details in that request.