[PR] web/security: Explain where to report CVE#s (PR #2)

PR #2 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/web/pulls/2
Patch URL: https://code.ffmpeg.org/FFmpeg/web/pulls/2.patch

Signed-off-by: Michael Niedermayer <[email protected]>


>From e2fec87df2a4da485e377d9f58c8997aaf821e70 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer <[email protected]>
Date: Mon, 22 Jun 2026 02:42:02 +0200
Subject: [PATCH] web/security: Explain where to report CVE#s

Signed-off-by: Michael Niedermayer <[email protected]>
---
 src/security | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/security b/src/security
index 8861ee8..a5e489c 100644
--- a/src/security
+++ b/src/security
@@ -20,6 +20,16 @@ And that you provide a easy to use testcase. Automated submissions are not accep
   <li>Any CVE identifier or other related identifier, if available.</li>
 </ol>
 
+<h3>Contributing missing CVE identifiers</h3>
+<p>The list of CVEs on this page is maintained by the FFmpeg community. If you register a CVE or find one missing from the lists below, please help keep it up to date:</p>
+
+<h4>Before the fix has been backported to release branches</h4>
+<p>Please email <a href="mailto:[email protected]">[email protected]</a> with the CVE identifier and the git commit that fixes it.</p>
+
+<h4>After the fix has been backported</h4>
+<p>Please <a href="https://code.ffmpeg.org/FFmpeg/web/pulls">open a pull request</a> against the web repository to add the entry to the relevant section(s) of this page.</p>
+
+
 <h2>FFmpeg git master</h2>
 <p>
 Fixes following vulnerabilities:
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]