Loading story…
Penpot disclosed and fixed CVE-2026-45805, a high-severity remote code execution flaw in its MCP component affecting versions earlier than 2.15.0. The issue stemmed from ReplServer.ts binding a REPL service to 0.0.0.0:4403 and exposing an unauthenticated /execute endpoint that passed attacker-controlled input to PluginBridge.executePluginTask(), allowing arbitrary JavaScript execution by anyone with network access. The CVE was assigned CWE-749 and a CVSS v3.1 score reflecting high impact to confidentiality, integrity, and availability.
Project fixes moved the MCP REPL binding to localhost and shipped alongside broader security hardening in Penpot, including protections against SSRF, stored XSS, CSS injection through font family validation, and incorrect invitation token handling during registration. The vulnerability record also notes proof-of-concept exploitation metadata and links to the fixing commit, release notes, issue tracker, and GitHub security advisory, with remediation available in Penpot 2.15.0.
Map this exposure pattern across your cloud, code, and identities.
2 events from the most recent confirmed update back to the earliest known activity.
The vulnerability was cataloged as CVE-2026-45805, affecting Penpot versions earlier than 2.15.0, with details describing unauthenticated code execution via the MCP REPL server. The CVE record was received on July 15, 2026 and modified the same day to add a GitHub advisory reference and SSVC metadata.
Penpot fixed a vulnerability in its MCP component by changing the REPL server behavior so it no longer exposed an unauthenticated /execute endpoint bound to 0.0.0.0, addressing remote JavaScript execution on the server. The fix is referenced in Penpot release materials and code changes associated with version 2.15.0.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See where this exposure pattern shows up across your cloud, code, supply chain, and non-human identities.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Chainlit released version **2.12.0** to remediate two unauthenticated vulnerabilities in its Model Context Protocol `/mcp` endpoint: critical command injection/RCE, **CVE-2026-45018** (CVSS 9.8), and high-severity SSRF, **CVE-2026-45019** (CVSS 7.2). Versions `2.4.0rc0` through `2.11.x` are affected when `features.mcp.enabled = true`. The command-injection issue allowed attackers to submit client-controlled stdio `fullCommand` values; configurations with no `allowed_executables` restriction could allow arbitrary commands through permitted tooling such as `npx -c`, executing under the Chainlit process account. The SSRF issue let attackers supply arbitrary HTTP/SSE MCP URLs and headers, enabling requests to loopback and private-network services, Docker sockets, Kubernetes APIs, databases, and cloud metadata endpoints such as `169.254.169.254`, with possible exposure of temporary cloud credentials. Version 2.12.0 requires server-side named configuration for stdio MCP servers and adds explicit opt-in allowlisting, destination revalidation, sensitive-header filtering, and redirect blocking for user-provided HTTP/SSE connections. Organizations should upgrade promptly; where that is not immediately possible, disable MCP with `features.mcp.enabled = false`, enforce authentication, and block server egress to internal networks and cloud-metadata services.
Aug 26, 2026
Researchers disclosed multiple security flaws affecting AWS MCP components, including a local file inclusion bug in the AWS Remote MCP Server and a critical command injection issue in `aws-mcp-server`. Varonis said authenticated users could abuse AWS CLI shorthand syntax, specifically the `@=` operator passed through the `aws___call_aws` tool, to read arbitrary files from the underlying host even when `FileAccessMode=NO_ACCESS` was enabled. AWS assigned **CVE-2026-4270** to the file access restriction bypass and said the issue was fixed in `aws-api-mcp-server` version **1.3.9**; the exposure affected the public endpoint `aws-mcp.us-east-1.api.aws` as well as self-hosted or forked deployments. A separate flaw, tracked as **CVE-2026-5058** and published by Trend Micro's Zero Day Initiative as **ZDI-26-246**, allows unauthenticated remote code execution in `aws-mcp-server` because user-supplied input in the allowed-commands list is not properly validated before being used in a system call. ZDI rated the bug **CVSS 9.8** and said successful exploitation lets attackers run arbitrary code in the MCP server context; the advisory was released as a 0-day after the vendor rejected the report. The disclosures landed alongside another AWS bulletin for **CVE-2026-4269**, an improper S3 ownership verification issue in the Bedrock AgentCore Starter Toolkit, underscoring broader security concerns around MCP-related tooling and the need for immediate patching and review of derivative implementations.
Jun 29, 2026
Anthropic fixed three vulnerabilities in its official *Git MCP server* (`mcp-server-git`) that could be triggered via **prompt injection** and chained with other MCP tools to achieve **remote code execution** or destructive file operations. The issues were reported by agentic AI security firm **Cyata**, which demonstrated that attacker-controlled content an AI assistant might read (for example, a malicious `README`, poisoned issue text, or other untrusted context) could drive the LLM to invoke MCP tool calls with crafted arguments, enabling exploitation without the attacker having direct access to the victim host. Cyata identified `CVE-2025-68143` (**unrestricted `git_init`**), `CVE-2025-68145` (**path validation bypass**), and `CVE-2025-68144` (**argument injection in `git_diff`**). In combination—particularly when `mcp-server-git` is used alongside the *Filesystem MCP server*—the flaws could enable code execution, arbitrary file deletion/overwrite, and reading arbitrary files into the LLM context (with Cyata noting this does not inherently provide direct exfiltration). The vulnerabilities affected default deployments of `mcp-server-git` prior to **version `2025.12.18`**; Anthropic was notified in June and shipped fixes in December, and there was no indication reported that the bugs were exploited in the wild.
Jun 29, 2026