Silent Lynx 利用 WinRAR 漏洞在独立国家联合体政府攻击中部署反向 Shell · 4h NGINX 修复 5 个漏洞,包括可能的 RCE 和可能跳过客户端证书检查的 TLS 漏洞 · 7h Next.js 发布了针对缓存和 SVG 处理中的两个关键 RCE 漏洞的紧急补丁 · 7h Drupal 修补了通过贡献模块无需登录路径的关键核心 RCE 漏洞 · 8h Sparx Systems Enterprise Architect软件中的漏洞 · 8h Curl 修复了由 Anthropic 发现的“高” RCE 漏洞 · 8h Slican电话交换机中的漏洞 · 9h Palo Alto Networks警告防火墙安全漏洞被滥用 · 12h 思科报告称Secure Email Gateway中的关键漏洞被积极利用 · 13h Langflow的关键认证远程代码执行漏洞在1,423次蜜罐攻击尝试中被针对 · 13h Silent Lynx 利用 WinRAR 漏洞在独立国家联合体政府攻击中部署反向 Shell · 4h NGINX 修复 5 个漏洞,包括可能的 RCE 和可能跳过客户端证书检查的 TLS 漏洞 · 7h Next.js 发布了针对缓存和 SVG 处理中的两个关键 RCE 漏洞的紧急补丁 · 7h Drupal 修补了通过贡献模块无需登录路径的关键核心 RCE 漏洞 · 8h Sparx Systems Enterprise Architect软件中的漏洞 · 8h Curl 修复了由 Anthropic 发现的“高” RCE 漏洞 · 8h Slican电话交换机中的漏洞 · 9h Palo Alto Networks警告防火墙安全漏洞被滥用 · 12h 思科报告称Secure Email Gateway中的关键漏洞被积极利用 · 13h Langflow的关键认证远程代码执行漏洞在1,423次蜜罐攻击尝试中被针对 · 13h
🛡️
ACyber Sentinel 安全评估团队
← 返回
⚠️ 漏洞报告

CVE-2026-97228

CVE-2026-97228 - Rapid7 Bulk Export MCP — GraphQL Query Injection in Export Status Lookup

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!`).

发布于: Sep 25, 2026 11:17

最后修改: Sep 25, 2026 13:26