Vulnerability in Rapid7 Bulk Export MCP (CVE-2026-97228)
Summary
Vulnerability in Rapid7 Bulk Export MCP (CVE-2026-97228). Risk of unauthorized operations or information disclosure. Exploitable via get_export_status.
Original description
The description as published by the source.
Rapid7 Bulk Export MCP versions 0.2.5 through 0.6.1 suffer from a GraphQL query injection issue in the export-status component (get_export_status in src/export_manager.py), whereby the export_id value — an unvalidated MCP tool argument reaching the function via the check_rapid7_export_status and download_rapid7_export tools — is interpolated directly into the GraphQL query string. A crafted export_id containing quote and brace characters can terminate the intended export(id: "...") selection early and append attacker-controlled root-level selections (for example, schema introspection), producing a single well-formed GraphQL document that is then sent to the Rapid7 export API under the operator's own API key.
Notably, this issue does not grant an existing actor any access they do not already have: every injected query executes within the operator's own already-authenticated API scope, using the operator's own valid API key, and cannot cross a tenant or account boundary. A directly-malicious operator gains nothing they could not already do by calling the API directly; the realistic exposure is limited to a compromised or careless upstream MCP client, or indirect prompt injection forwarding an unvalidated identifier. This is fixed in version 0.6.2, which passes export_id as a parameterized GraphQL variable ($exportId: ID!).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-97228 has been found in Rapid7 Bulk Export MCP.
Attackers can target a specific entry point like get_export_status over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 2.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Rapid7 Bulk Export MCP CVE-2026-97228" on the vendor's site.
CVE-2026-97228 (Rapid7 Bulk Export MCP) — CWE-943 / CVSS v3 2.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: get_export_status / export_id / check_rapid7_export_status / download_rapid7_export
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-943) exists in Rapid7 Bulk Export MCP. Attackers reach the vulnerable code path via get_export_status.
Check the vendor advisory for the affected versions of Rapid7 Bulk Export MCP. Attack surface: get_export_status / export_id / check_rapid7_export_status / download_rapid7_export.
Severity: Low (CVSS 2.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Rapid7 Bulk Export MCP を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web nvd.nist.gov
- web github.com