MCP server ships with test-mode endpoint enabled in production builds
Summary
MCP server left a `/__test/exec` endpoint enabled in its published Docker image. Accepts arbitrary command input with no auth. Attacker who finds the server at a discoverable path exec's on the host.
Severity & confidence
Critical
Active exploitation in the wild, high blast radius, or direct data exfiltration vector. Treat as an urgent remediation target; quarantine affected artifacts immediately.
Confirmed
Observed directly by Jiffy scanners or validated by multiple independent sources. Indicators are reliable enough to drive automated action.
Indicators
Observed patterns and artifacts associated with this entry. Each indicator can be copied into your detection stack or SIEM.
/__test/exec|/debug/exec
Detection rule
A YARA-style pseudo-rule auto-generated from the indicators above. Useful as a starting point — adapt the syntax for your target detection platform.
rule jiffy_ti_2026_000055
{
meta:
source = "jiffy-intel"
severity = "critical"
description = "Auto-generated from Jiffy Intel indicators"
strings:
$endpoint_0 = "/__test/exec|/debug/exec"
condition:
$endpoint_0
}Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.
Affected tools
| Tool | Versions | Status |
|---|---|---|
| Any MCP-capable agent | * | vulnerable |
Example artifacts
Sanitized examples of artifacts Jiffy has observed exhibiting this pattern. Publisher handles are redacted; version ranges and status reflect the most recent scan.
- ops-harness-mcpMCP serverRemoved
- ci-harness-mcpMCP serverQuarantined
How to remediate
- 01Rebuild affected MCP server images without test endpoints.
- 02Expose narrow tool surface only.
Timeline & sources
Timeline
- First observedMar 25, 202623 days ago
- Last updatedApr 27, 2026today
- PublishedApr 2, 202615 days ago
Sources
References
Scan for patterns like this
Point Jiffy at your GitHub org, IDE config, or a single artifact. Get a scored report in under a minute.
Start a free scan