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

Information Disclosure in github.com/basekick-labs/arc (CVE-2026-48050)

Summary

Vulnerability in github.com/basekick-labs/arc (CVE-2026-48050). Risk of unauthorized operations or information disclosure. Exploitable via PublicPrefixes. Mitigation: upgrade to 0.0.0-20260520170331-32a4091fb949 or later.

Original description

The description as published by the source.

Summary

Arc registers Go's net/http/pprof handlers at /debug/pprof/* via app.Use(pprof.New()) in internal/api/server.go, and /debug/pprof is added to PublicPrefixes in cmd/arc/main.go. The auth middleware short-circuits before the token check on prefix match, so the endpoints are reachable without any authentication.

Impact

Any network-reachable caller (no token required) can:

  • Fetch /debug/pprof/heap — leaks in-memory state: live SQL strings, decoded msgpack records, decompressed request bodies, cached *TokenInfo (the auth cache keys on SHA-256 of the plaintext token at auth.go:543).
  • Fetch /debug/pprof/goroutine?debug=2 — leaks call stacks, identifying internal code paths.
  • Fetch /debug/pprof/profile?seconds=N — pins a CPU core for arbitrary duration. Trivial DoS amplification (one short HTTP request → minutes of server CPU).
  • Fetch /debug/pprof/trace — long-duration execution trace, similar DoS profile.

No authentication, no rate limiting, no resource bound on the seconds parameter.

Patches

https://github.com/Basekick-Labs/arc/releases/tag/v26.06.1

Planned mitigation:

  1. Gate pprof registration behind an env var (ARC_DEBUG_PPROF=1) that defaults to off.
  2. When enabled, bind pprof to a separate localhost-only listener (127.0.0.1:6060 via dedicated net/http server) so it's never reachable from the public API port.
  3. Remove /debug/pprof from PublicPrefixes.
  4. Fix the HasPrefix bug where "/debug/pprofX" matc…

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-48050 has been found in github.com/basekick-labs/arc.
Attackers can target a specific entry point like PublicPrefixes over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/basekick-labs/arc to 0.0.0-20260520170331-32a4091fb949 or later.
If unsure, ask your IT team or search "github.com/basekick-labs/arc CVE-2026-48050" on the vendor's site.

CVE-2026-48050 (github.com/basekick-labs/arc) — CWE-200
Attack surface: PublicPrefixes / seconds / HasPrefix
Patched: 0.0.0-20260520170331-32a4091fb949 — 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

Information disclosure (CWE-200) exists in github.com/basekick-labs/arc. Attackers reach the vulnerable code path via PublicPrefixes.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/basekick-labs/arc. Attack surface: PublicPrefixes / seconds / HasPrefix.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260520170331-32a4091fb949.

🛡️ 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/basekick-labs/arc' . 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/basekick-labs/arc' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/basekick-labs/arc to 0.0.0-20260520170331-32a4091fb949

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

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

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

Affected packages

go github.com/basekick-labs/arc
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260520170331-32a4091fb949"}]}]

References

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