Do not open a public GitHub issue for security vulnerabilities.

Report privately via one of:

1. GitHub Private Vulnerability Reporting (preferred) — report here.
2. Email — security@knowledgestack.ai (include "ks-microsoft-word-agent" in the subject).

Please include where possible:

• Affected version (commit SHA or release tag)
• Reproduction steps
• Impact (credential / document exposure, code execution, privilege escalation, DoS)
• Proof-of-concept if you have one

Things we treat seriously:

• Credential leakage — the add-in stores a KS API key in Office.js roaming settings. Issues around key exposure in logs, error messages, or cross-user leakage are in scope.
• Document content exfiltration — any path that leaks document content to an unauthorized party (wrong tenant, wrong user, external service not in the documented data flow).
• Content-script / prompt injection — malicious document content that coerces the add-in into tool misuse.
• Supply chain — vulnerabilities in our hosted frontend bundle or the manifest we distribute.

Out of scope (report elsewhere):

• Vulnerabilities in the hosted Knowledge Stack API — security@knowledgestack.ai directly.
• Issues in Microsoft's Office.js runtime or Word itself — report to Microsoft.
• Vulnerabilities in forked / modified copies of this add-in.

• Acknowledgement within 2 business days
• Triage within 5 business days
• Critical fixes target 7 days
• Default disclosure window: 90 days from report, adjusted by mutual agreement

Good-faith research welcomed under the same terms as the rest of the Knowledge Stack ecosystem. Please avoid destruction of data and disruption of service, only test accounts you own, and give us time to fix before public disclosure.