Summary
CVE-2026-86242 is an unauthenticated remote code execution vulnerability in the Bifrost HTTP transport (maximhq/Bifrost) affecting all versions prior to 2.0.0. It allows an attacker to register a custom plugin whose path is an HTTP URL via an unauthenticated API endpoint, causing the server to download and load attacker-controlled code. The issue carries a CVSS v3.1 base score of 8.1 (High).
Technical details
- Root cause: the plugin-registration endpoint accepts a plugin "path" value that is an HTTP URL; the transport downloads the response body, writes it to a temporary shared-object file, and loads it via Go’s dynamic plugin loader, then invokes an initialization routine with attacker-supplied configuration.
- Trigger conditions: management authentication is disabled, which is the default configuration (
governance.auth_config.is_enabled=false); no credentials are required to reach the plugin endpoint. - Attack vector: network-reachable, unauthenticated
POSTrequest to the plugin management API; no user interaction required. - Impact: on dynamically linked builds (the build type required to support custom Go plugins), successful loading of the attacker-supplied shared object results in arbitrary code execution as the Bifrost process user, with full loss of confidentiality, integrity, and availability. On statically linked builds (e.g., the published Docker image), dynamic loading fails, and the vulnerability instead results in server-side request forgery rather than code execution.
Affected software
- maximhq Bifrost, HTTP transport, all versions before 2.0.0 (unaffected as of 2.0.0-prerelease3)
- Impacted platforms: Linux, macOS
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: upgrade to Bifrost HTTP transport version 2.0.0 or later (fix released as transports/v2.0.0).
- If unable to patch immediately: enable management authentication (
governance.auth_config.is_enabled=true) so the plugin-registration endpoint requires credentials, and restrict network access to the Bifrost management/API interface to trusted hosts only.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
id="bifrost-shell", a scriptsrccontainingbifrost-logo.webp, a scriptsrccontainingbifrost-logo-dark.webp

