From 8f5af75f47d930c1c7452abc63b06bdae8c6fcce Mon Sep 17 00:00:00 2001 From: Kevin Allioli Date: Thu, 12 Nov 2026 16:11:49 +0100 Subject: [PATCH] docs(security): report through GitHub private vulnerability reporting --- SECURITY.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index ea7b0c5..a33b016 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -8,11 +8,14 @@ and `oic-sync`. Do **not** describe a vulnerability in a public issue. -A private reporting channel is not set up yet: GitHub private vulnerability reporting is not -enabled on the organization's repositories and no security contact is published. Until it is, -open a public issue in [`open-img-cloud/.github`](https://github.com/open-img-cloud/.github/issues) -titled "Security contact request", without any detail, and a maintainer will arrange a private -channel. +Report it privately through GitHub: open the **Security** tab of the affected repository and +choose **Report a vulnerability** (private vulnerability reporting is enabled on every +repository of the organization). For the build pipeline, use +[`open-img-cloud/.github`](https://github.com/open-img-cloud/.github/security/advisories/new); +for the image distribution service, [`open-img-cloud/images-router`](https://github.com/open-img-cloud/images-router/security/advisories/new); +for a specific image, its own repository. When unsure, use `open-img-cloud/.github`. + +The report stays visible only to you and the maintainers until a fix is published. Vulnerabilities in the software inside an image (kernel, OpenSSL, cloud-init...) belong to the upstream distribution: report them there. The project republishes fixed images when the