Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55245

SSRF (Server-Side Request Forgery) in github.com/maximhq/bifrost/core (CVE-2026-55245)

Summary

SSRF in github.com/maximhq/bifrost/core (CVE-2026-55245). Risk of unauthorized operations or information disclosure. Exploitable via isPublicIP. Mitigation: upgrade to 1.5.17 or later.

Original description

The description as published by the source.

Summary

isPublicIP in core/providers/utils/fetch.go — the SSRF deny-list that gates FetchAndEncodeURL — does not reject several routable address ranges that map onto internal infrastructure. Carrier-Grade NAT (100.64.0.0/10, RFC 6598), IPv6 6to4 (2002::/16), NAT64 (64:ff9b::/96 and 64:ff9b:1::/48), and deprecated IPv6 site-local (fec0::/10) are all classified as public and permitted. An attacker who controls a multimodal image/document URL in a Bedrock or Vertex request body can drive the gateway to fetch internal services it should not reach — including the cloud instance-metadata endpoint via the 6to4 / NAT64 embeddings of 169.254.169.254.

The rest of the fetch hardening is correct and is not part of this report: the dial-time LookupIP + pin to ips[0] closes the DNS-rebinding TOCTOU, CheckRedirect re-validates redirect targets, the scheme gate, the 25 MiB cap, and the 20 s timeout all work. This is purely a residual IP-classification gap in isPublicIP.

Affected component

  • File: core/providers/utils/fetch.go, function isPublicIP (lines 107-118), reached only through FetchAndEncodeURL (line 28).
  • Go module: github.com/maximhq/bifrost/core
  • Version: confirmed on the current dev HEAD f415c144678bd4b411d74a1c1f85f18652833224 (core/version = 1.5.15).

Vulnerable code

func isPublicIP(ip net.IP) bool {
	addr, ok := netip.AddrFromSlice(ip)
	if !ok {
		return false
	}
	addr = addr.Unmap()
	if addr.IsLoopback() || ad…

Source: GitHub Security Advisories (Global) 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-55245 has been found in github.com/maximhq/bifrost/core.
Attackers can target a specific entry point like isPublicIP over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/maximhq/bifrost/core to 1.5.17 or later.
If unsure, ask your IT team or search "github.com/maximhq/bifrost/core CVE-2026-55245" on the vendor's site.

CVE-2026-55245 (github.com/maximhq/bifrost/core) — CWE-918
Attack surface: isPublicIP / FetchAndEncodeURL / LookupIP / CheckRedirect
Patched: 1.5.17 — 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

SSRF (CWE-918) exists in github.com/maximhq/bifrost/core. Attackers reach the vulnerable code path via isPublicIP.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/maximhq/bifrost/core. Attack surface: isPublicIP / FetchAndEncodeURL / LookupIP / CheckRedirect.

🔥 Severity

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

🔧 How to fix

Update to 1.5.17.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'github.com/maximhq/bifrost/core' . 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/maximhq/bifrost/core' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/maximhq/bifrost/core to 1.5.17

    ステージング環境で 1.5.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/maximhq/bifrost/core
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.5.17"}]}]

References

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