CVE-2026-46492: XSS in md-fileserver Markdown Rendering

Technical summary

The vulnerability exists in md-fileserver's markdown rendering pipeline, which processes user-supplied markdown without HTML sanitization. The application passes raw HTML through to the DOM, enabling CWE-80 (Improper Neutralization of Script-Related HTML Tags) and CWE-87 (Improper Neutralization of Alternate XSS Syntax). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C) indicates network-based exploitation with no prerequisites—any markdown file served by the application can trigger the flaw, and the scope is changed, meaning the impact affects resources beyond the vulnerable component itself. The vulnerability was remediated by implementing proper HTML escaping or a content security model that strips or neutralizes script-bearing elements before rendering.

Business impact

Organizations using md-fileserver in multi-user or externally-facing environments face significant risk. An attacker who can control or inject markdown content—through file uploads, compromised documentation repositories, or social engineering—can execute JavaScript in the context of viewers' browsers. This can lead to session hijacking, credential theft, malware distribution, or defacement of content. Teams relying on this tool for collaborative documentation, knowledge bases, or static site generation should prioritize remediation to prevent unauthorized access to sensitive information or privilege escalation.

Affected systems

md-fileserver versions prior to 1.10.3 are affected. The vulnerability requires no special configuration or authentication to exploit if the application is network-accessible. Any deployment exposing the application over HTTP(S)—whether internal or public—is at risk. Users should verify their installed version and cross-reference against vendor documentation to confirm whether patches are available for their deployment.

Exploitability

Exploitation is straightforward and requires only that a user views a malicious markdown file in md-fileserver. No user interaction beyond opening the file is needed (UI:N in the CVSS vector). An attacker can distribute a booby-trapped .md file via email, file sharing, or by compromising a markdown repository. The low complexity (AC:L) and lack of authentication requirements (PR:N) make this a practical attack vector in real-world scenarios. Public repositories or shared drive scenarios amplify risk significantly.

Remediation

Upgrade md-fileserver to version 1.10.3 or later immediately. This patch implements proper HTML sanitization in the markdown rendering logic. If an immediate upgrade is not feasible, implement network controls to restrict access to the application (firewall rules, VPN gating, or IP whitelisting) and educate users to avoid opening untrusted markdown files. Consider disabling markdown rendering of raw HTML altogether if the use case permits.

Patch guidance

Apply version 1.10.3 or any later stable release from the vendor. Verify the patch through the official md-fileserver repository or release notes. Test the patched version in a staging environment before production deployment to ensure compatibility with existing workflows and that no regressions are introduced. Document the patch date and version in your asset inventory.

Detection guidance

Monitor application logs for unusual markdown file access patterns or abnormally large or malformed markdown payloads. Use a Web Application Firewall (WAF) to inspect for common XSS signatures within markdown content (e.g., <script>, onerror=, javascript: protocols). Endpoint Detection and Response (EDR) tools should flag unexpected child processes spawned by browser processes viewing md-fileserver content. Code review tools can scan markdown files for embedded HTML tags in shared repositories. Server-side Content Security Policy headers can mitigate some payload execution even on unpatched systems.

Why prioritize this

The CVSS score of 7.2 (HIGH) reflects a network-accessible vulnerability with low complexity and no authentication barriers. The changed scope (S:C) indicates cross-domain impact. While confidentiality and integrity impact are rated low in the vector, the practical consequence of arbitrary JavaScript execution is significant in collaborative or public-facing deployments. Organizations should prioritize patching within days, not weeks, especially if markdown files are shared externally or processed in high-trust environments.

Risk score, explained

The CVSS 3.1 score of 7.2 is driven by: (1) network-based attack vector requiring no special access; (2) low attack complexity with no prerequisites; (3) no authentication or user interaction required, though markdown must be viewed; (4) changed scope indicating the vulnerability can impact services or data outside the application itself; and (5) direct impact on confidentiality and integrity through arbitrary code execution. The score does not reflect availability impact, as the vulnerability does not inherently cause denial of service, though executed payloads could theoretically do so.

Frequently asked questions