Summary
CVE-2026-55245 is a Server-Side Request Forgery (SSRF) vulnerability in Bifrost, an AI gateway used to route requests to model providers. The flaw lies in the isPublicIP validation function used to filter outbound URLs for multimodal (image/document) requests, and it fails to block several routable address ranges that can resolve to internal or cloud-metadata infrastructure. The issue is rated HIGH severity with a CVSS v4.0 base score of 8.7.
Technical details
- Root cause: the
isPublicIPfunction incore/providers/utils/fetch.gorelies onaddr.IsPrivate()andUnmap(), which do not account for Carrier-Grade NAT (100.64.0.0/10), IPv6 6to4 (2002::/16) and NAT64 (64:ff9b::/96, 64:ff9b:1::/48) embedded addresses, or deprecated IPv6 site-local addresses (fec0::/10). - Trigger condition: a client supplies a URL for a multimodal (image/document) request that is processed by
FetchAndEncodeURL, used by the Bedrock and Vertex provider integrations. - Attack vector: network, no authentication or user interaction required; an attacker controls the fetched URL and encodes a disallowed address inside an allowed representation (e.g., 6to4/NAT64 encodings of 169.254.169.254).
- Impact: the gateway can be coerced into fetching internal network resources or cloud instance metadata endpoints, potentially exposing sensitive internal data or credentials.
Affected software
- Bifrost Core versions ≤ 1.5.15 (fixed in 1.5.16 and later)
Severity
- CVSS v4.0 Base Score: 8.7 (HIGH)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade Bifrost Core to version 1.5.16 or later, which adds explicit checks for CGNAT ranges, validates embedded IPv4 addresses extracted from 6to4/NAT64 representations, and rejects deprecated site-local addressing.
- If immediate patching is not possible: restrict outbound network access from the Bifrost gateway to internal/private address ranges and cloud metadata endpoints at the network or firewall layer, and disable or closely monitor multimodal (image/document URL) request handling for Bedrock/Vertex providers until patched.
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",src="bifrost-logo.webp",src="bifrost-logo-dark.webp"

