From d9e4449fca3bc4c0eac19858db159264c15f25f6 Mon Sep 17 00:00:00 2001
From: Sony Mathew <2040199+sony-mathew@users.noreply.github.com>
Date: Mon, 27 Jul 2026 18:01:22 +0530
Subject: [PATCH] docs: update security reporting policy

---
 .github/workflows/broken-links-check.yml |  4 +++
 .nvmrc                                   |  2 +-
 contributing-guide/security-reports.mdx  | 35 +++++++++++++++++++++++-
 3 files changed, 39 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/broken-links-check.yml b/.github/workflows/broken-links-check.yml
index 811f8738..450ed54b 100644
--- a/.github/workflows/broken-links-check.yml
+++ b/.github/workflows/broken-links-check.yml
@@ -13,6 +13,10 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: .nvmrc
       - name: Install Mint
         run: npm i -g mint
       - name: Broken Link Check
diff --git a/.nvmrc b/.nvmrc
index 7cc20699..db49bb14 100644
--- a/.nvmrc
+++ b/.nvmrc
@@ -1 +1 @@
-20.5.1
+22.22.2
diff --git a/contributing-guide/security-reports.mdx b/contributing-guide/security-reports.mdx
index d7e57312..542a9957 100644
--- a/contributing-guide/security-reports.mdx
+++ b/contributing-guide/security-reports.mdx
@@ -22,6 +22,14 @@ Please try your best to describe a clear and realistic impact for your report, a
 Please use the email for questions related to the process. Disclosures should be done via [GitHub](https://github.com/chatwoot/chatwoot/security/advisories/new).
 </Note>
 
+## Report Quality and Duplicates
+
+Please include clear steps to reproduce, a realistic impact, the affected version, and any required configuration details.
+
+We may close reports that are theoretical, scanner-only, AI-generated without verification, or missing enough detail for us to reproduce the issue.
+
+If the same vulnerability was reported before, we will close later reports as duplicates and link them to the canonical report. The canonical report is the earliest valid report we received for that issue.
+
 ## Supported Versions
 
 | Version  | Supported |
@@ -59,7 +67,6 @@ We consider the following out of scope, though there may be exceptions:
 - Weak SSL/TLS/SSH algorithms or protocols
 - Attacks involving physical access to a user's device or a device or network that's already seriously compromised (e.g., man-in-the-middle)
 - The user attacks themselves
-- Incomplete/Missing SPF/DKIM
 - Denial of Service attacks
 - Brute force attacks
 - DNSSEC
@@ -84,6 +91,32 @@ After triage, the team will start working on the issue based on the following se
 | Medium        | 60 Days   |
 | Low           | 90 Days   |
 
+## Advisory and CVE Publishing
+
+We publish security advisories and CVEs at [GitHub Security Advisories](https://github.com/chatwoot/chatwoot/security).
+
+We request or publish a CVE when the issue is a confirmed, externally exploitable vulnerability in a supported Chatwoot release, and users or operators need a stable public identifier to assess impact, upgrade, or track exposure.
+
+We usually request a CVE for:
+
+- Critical or high-impact vulnerabilities such as remote command execution, SQL injection, authentication bypass, privilege escalation, meaningful XSS, or CSRF with real impact
+- Cross-tenant data exposure, token or credential exposure, and account takeover paths
+- Fixed vulnerabilities where affected versions and patched versions are known
+- Unrelated vulnerabilities reported together, if they are independently fixable
+
+We do not request a new CVE for:
+
+- Duplicate reports of an already-covered vulnerability
+- Scanner-only or theoretical reports without demonstrated exploitability
+- Out-of-scope items such as missing headers, SPF/DKIM, brute force, DNSSEC, or broad denial-of-service reports
+- Issues that only affect unsupported old versions, unless there is strong public coordination value
+- Dependency vulnerabilities already covered by an upstream CVE
+- Pure hardening or defense-in-depth changes without a demonstrated vulnerability
+
+Multiple reports of the same issue will be covered by one advisory or CVE, using the canonical earliest report.
+
+During triage and fix work, we keep the GitHub Security Advisory private. Once the issue is confirmed and likely publishable, we may request or reserve a CVE. We publish the advisory and CVE when the fix is released, ideally with affected versions, the patched version, impact, workaround, and credits. If there is active exploitation or unavoidable disclosure pressure, we may publish earlier with mitigation guidance.
+
 ## Security Best Practices
 
 ### For Researchers