CVE-2026-8661: Server-Side Cross-Site Scripting and SSRF in Rapid7 InsightConnect Markdown to PDF Plugin
Server-Side Request Forgery in the markdown_to_pdf action of Rapid7 InsightConnect Markdown Plugin on Linux in versions prior to 4.0.2 allows remote attackers to make arbitrary outbound HTTP requests via unsanitized resource-loading HTML elements (img/src, CSS url(), @import) embedded in Markdown input. The initial fix in 4.0.0 disabled JavaScript but did not neutralize resource-loading vectors. Resolved in 4.0.2 by sanitizing HTML with an allowlist of tags, attributes, and URL schemes.
Security readout for executives and security teams
Plain-English summary
A flaw in Rapid7's InsightConnect Markdown Plugin can make a Linux automation worker contact attacker-chosen network locations when converting untrusted Markdown to PDF. This could expose limited data or affect downstream systems reachable from the worker. JavaScript blocking alone is insufficient; version 4.0.2 adds HTML and URL allowlisting.
Executive priority
Treat this as a targeted, moderate-priority remediation. Patch promptly where untrusted content enters PDF workflows or workers can reach sensitive internal services. Lower-risk, tightly controlled deployments can follow normal patch cadence after confirming input trust and outbound restrictions. No evidence provided supports emergency incident status.
Technical view
Before 4.0.2, the markdown_to_pdf action permitted outbound resource loading through HTML image sources and CSS URL or import constructs. This creates SSRF and server-side cross-site scripting risk. Version 4.0.0 disabled JavaScript but left these resource-loading paths open. CVSS 3.1 is 4.8: network-accessible, high complexity, no privileges or interaction, with low confidentiality and integrity impact.
Likely exposure
Exposure requires the Linux InsightConnect Markdown Plugin before 4.0.2, attacker-influenced Markdown reaching markdown_to_pdf, and useful outbound network access from the worker. Internet-facing access is not established by the sources. Environments accepting untrusted Markdown or permitting worker access to sensitive internal services deserve priority review.
Exploitation context
The supplied record is not in CISA KEV, and the cited sources do not establish active exploitation. Exploitation is constrained by high attack complexity, but requires neither authentication nor user interaction according to the CVSS vector. The practical impact depends heavily on workflow input controls and network reachability from the plugin runtime.
Researcher notes
The record explicitly states versions before 4.0.2 are affected and describes 4.0.2's allowlist remediation. However, the supplied affected-version structure is ambiguous, contains no CPEs, and declares a default unaffected status. Validate inventory against Rapid7's plugin versioning. The sources provide no confirmed exploitation, observed indicators, or detailed environmental impact evidence.
Mitigation direction
Upgrade the InsightConnect Markdown Plugin to version 4.0.2 or later.
Identify workflows passing user-controlled or externally sourced Markdown into markdown_to_pdf.
Restrict untrusted Markdown conversion until affected plugin instances are upgraded.
Limit worker outbound access to required destinations and sensitive internal services.
Review Rapid7 guidance and the referenced patches for deployment-specific considerations.
Validation and detection
Inventory Linux InsightConnect Markdown Plugin instances and confirm their installed versions.
Verify every affected instance runs version 4.0.2 or later.
Trace markdown_to_pdf inputs and identify externally controlled Markdown sources.
Confirm HTML sanitization enforces allowed tags, attributes, and URL schemes.
Review available network telemetry for unexpected outbound requests from conversion workers.
Test remediation safely with approved benign resources in an isolated environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.