Categories
CVE-2026-77339

Vulnerability in github.com/f1bonacc1/process-compose (CVE-2026-77339)

Summary

Vulnerability in github.com/f1bonacc1/process-compose (CVE-2026-77339). Risk of unauthorized operations or information disclosure. Exploitable via GET /sse. Mitigation: upgrade to 1.120.0 or later.

Original description

The description as published by the source.

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:

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:

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 retur…

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-77339 has been found in github.com/f1bonacc1/process-compose.
Attackers can target a specific entry point like GET /sse over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/f1bonacc1/process-compose to 1.120.0 or later.
If unsure, ask your IT team or search "github.com/f1bonacc1/process-compose CVE-2026-77339" on the vendor's site.

CVE-2026-77339 (github.com/f1bonacc1/process-compose) — CWE-306
Attack surface: GET /sse / d56aa59df04b72f8644811ac581a051bec05e485 / initialize / pc_process_list
Patched: 1.120.0 — apply immediately
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.

❓ What is the problem

A vulnerability (CWE-306) exists in github.com/f1bonacc1/process-compose. Attackers reach the vulnerable code path via GET /sse.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/f1bonacc1/process-compose. Attack surface: GET /sse / d56aa59df04b72f8644811ac581a051bec05e485 / initialize / pc_process_list.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.120.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /sse requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/f1bonacc1/process-compose' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/f1bonacc1/process-compose' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/f1bonacc1/process-compose を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /sse' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /sse への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade github.com/f1bonacc1/process-compose to 1.120.0

    ステージング環境で 1.120.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /sse on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/f1bonacc1/process-compose
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.120.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details