Security: microsoft/fluentui-blazor

Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet, Xamarin, and our GitHub organizations.

If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's Microsoft's definition of a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.

If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the Microsoft Security Response Center PGP Key page.

You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

• Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the manifestation of the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our Microsoft Bug Bounty Program page for more details about our active programs.

We prefer all communications to be in English.

Microsoft follows the principle of Coordinated Vulnerability Disclosure.

The Fluent UI Blazor MCP Server is a read-only documentation provider designed with security in mind:

• ✅ No code execution capabilities
• ✅ No network access required
• ✅ Read-only operations only
• ✅ Sandboxed by IDE runtime
• ✅ No access to sensitive data

The MCP Server operates within strict security boundaries:

┌─────────────────────────────────────────────┐
│        Developer Workstation                │
│  ┌──────────────┐      ┌──────────────┐     │
│  │     IDE      │◄────►│  MCP Server  │     │
│  │ (VS/VS Code) │ stdio│   (Local)    │     │
│  └──────────────┘      └──────────────┘     │
│                               │             │
│                               ▼             │
│                        ┌──────────────┐     │
│                        │ Embedded JSON│     │
│                        │Documentation │     │
│                        └──────────────┘     │
└─────────────────────────────────────────────┘

• ❌ Execute arbitrary code
• ❌ Access your source code or workspace files
• ❌ Make network requests
• ❌ Modify files or system state
• ❌ Access environment variables or credentials
• ❌ Launch other processes
• ❌ Access system resources outside its scope

Security vulnerabilities in the MCP Server should be reported if they:

• Allow code execution beyond serving documentation
• Enable file system access outside the documentation directory
• Create network communication channels
• Bypass process isolation
• Expose sensitive information
• Allow privilege escalation

For comprehensive security information including threat model, compliance considerations, and security checklists, see our Security & Compliance Documentation.

Topics covered:

• Architecture and isolation details
• Threat model analysis
• Compliance considerations (GDPR, SOC 2, ISO 27001, HIPAA, PCI DSS)
• Audit procedures and monitoring
• Security best practices
• Security approval checklist