/

CVE-2026-90898

Severity:

CRITICAL RISK

(9.8)

Unauthenticated Command Execution (CWE-306) in Bifrost MCP

CVE-2026-90898

Awaiting Analysis

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-284, CWE-306

Impact:

Unauthenticated Remote Command Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Bifrost can start a registered stdio MCP client immediately through its management API, without requiring an MCP handshake. When authentication is disabled and an attacker can reach the API, an unauthenticated request may cause an arbitrary program to run with the privileges of the Bifrost gateway process.

Affected context

The vulnerability occurs in Bifrost deployments that expose the MCP client registration management API while governance authentication is disabled or ineffective. A stdio client is represented by a command and its arguments, and the gateway may launch that command as soon as the client is added. The affected behavior is associated with the transports v2.0.0 implementation; later transport behavior may reject unauthenticated stdio registration.

Exploit preconditions

  • Attack surface: Bifrost management API, specifically MCP client registration
  • Required access: Network reachability to the API; no credentials are required when authentication is disabled
  • Trigger point: Adding a stdio MCP client through the client-registration endpoint
  • Why exploitation is possible: The API treats unauthenticated callers as local administrators and starts the supplied command before an MCP handshake is required

Why this happens

The underlying flaw is a missing authentication and authorization boundary around an operation that launches operating-system processes. When authentication is disabled, the management API permits unauthenticated callers to perform an administrative registration action and supplies executable command data to the gateway. This maps primarily to CWE-306: Missing Authentication for Critical Function, with CWE-284: Improper Access Control also describing the failure to restrict process-launching functionality to authorized administrators.

Potential impact

  • An attacker may execute arbitrary programs as the Bifrost process user
  • The attacker could access application data and environment-provided secrets available to that user
  • The Bifrost gateway may be modified, disrupted, or used for further attacks
  • The host or container could be used for lateral movement, depending on network and runtime privileges
  • Service integrity and availability may be compromised

General mitigation guidance

Mitigation generally focuses on protecting process-launching management operations and reducing the trust placed in API input.

Common defensive patterns include:

  • Enable authentication and require authorization for MCP client registration
  • Avoid treating unauthenticated callers as administrative users, including in default configurations
  • Enforce server-side allowlists for permitted stdio executables and arguments
  • Prefer controlled, declarative integrations that do not accept arbitrary commands
  • Require explicit validation and policy checks before starting a registered process
  • Run the gateway with a dedicated least-privileged identity and restrict filesystem, network, and secret access
  • Bind management endpoints to trusted networks or administrative interfaces where appropriate
  • Apply deny-by-default process and egress policies around the gateway runtime

How teams detect issues like this

Detection can combine API monitoring, configuration review, and source analysis.

Useful approaches include:

  • Alert on unauthenticated requests to MCP client registration endpoints
  • Monitor for creation of stdio clients and unexpected child processes spawned by the Bifrost gateway
  • Review whether authentication defaults allow unauthenticated callers to reach administrative APIs
  • Use static analysis to identify process-launching code paths reachable from HTTP handlers without authorization checks
  • Flag command and argument fields that flow from API input into subprocess or equivalent execution APIs
  • Enforce CI policies requiring authentication and authorization annotations for administrative routes
  • Use automated code review tools to identify missing access-control checks and unrestricted command execution paths

Sources

SourceLink
github.comgithub.com/maximhq/bifrost
github.comgithub.com/maximhq/bifrost/commit/12e170352bd25eab1ae9ba16611f1797d1fd8fdc
github.comgithub.com/maximhq/bifrost/pull/6757
github.comgithub.com/maximhq/bifrost/releases/tag/transports/v2.1.0

Frequently asked

questions

Yes, when the Bifrost management API is network-reachable and authentication is disabled or otherwise bypassed. A caller may then register a stdio client without completing an MCP handshake.

The attacker needs connectivity to the MCP client registration endpoint. In the affected configuration, valid credentials are not required because unauthenticated callers are treated as local administrators.

Require authentication and explicit authorization for client registration, validate commands against a strict allowlist, and prevent arbitrary process-launching inputs from reaching the gateway runtime.

Apply deny-by-default access control to management APIs, test unauthenticated and low-privilege roles in security reviews, monitor child-process creation, and run gateways with minimal operating-system privileges.

Find out what's already
exploitable in your codebase.