How severe is GHSA-j93g-rp6m-j32m?

No CVSS score has been assigned to GHSA-j93g-rp6m-j32m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j93g-rp6m-j32m?

GHSA-j93g-rp6m-j32m affects the following packages: github.com/basekick-labs/arc (Go). Ecosystems affected: Go.

How do I fix GHSA-j93g-rp6m-j32m?

Update github.com/basekick-labs/arc to 0.0.0-20260520170331-32a4091fb949 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j93g-rp6m-j32m is resolved across your whole dependency graph.

How do I detect GHSA-j93g-rp6m-j32m in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/basekick-labs/arc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j93g-rp6m-j32m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j93g-rp6m-j32m?

O3 pinpoints whether GHSA-j93g-rp6m-j32m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j93g-rp6m-j32m actively exploited in the wild?

No public exploit code has been indexed for GHSA-j93g-rp6m-j32m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j93g-rp6m-j32m?

GHSA-j93g-rp6m-j32m has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j93g-rp6m-j32m?

GHSA-j93g-rp6m-j32m is classified as Information Exposure (CWE-200), Missing Authentication (CWE-306), Uncontrolled Resource Consumption (CWE-400). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j93g-rp6m-j32m published, and has it been updated?

GHSA-j93g-rp6m-j32m was published on June 11, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-j93g-rp6m-j32m

Fix: Basekick-Labs/arc@32a4091

GHSA-j93g-rp6m-j32m is a Information Exposure vulnerability in github.com/basekick-labs/arc. O3 Security confirms whether GHSA-j93g-rp6m-j32m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arc: Unauthenticated access to Go debug pprof endpoints leaks runtime state and enables CPU-burn DoS

Also known asCVE-2026-48050GO-2026-5457

Published

Jun 11, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/basekick-labs/arc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Gate pprof registration behind an env var (ARC_DEBUG_PPROF=1) that defaults to off.
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.
Remove /debug/pprof from PublicPrefixes.
Fix the HasPrefix bug where "/debug/pprofX" matches "/debug/pprof".

Workarounds

Block /debug/pprof* at a reverse proxy / load balancer in front of Arc.
Restrict Arc's API port to known-trusted networks via firewall rules.
Patch the running build: comment out app.Use(pprof.New()) in internal/api/server.go and rebuild.

Credits

Reported by Alex Manson (@NeuroWinter, https://neurowinter.com/) on 2026-05-19.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/basekick-labs/arc`	all versions	0.0.0-20260520170331-32a4091fb949

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/basekick-labs/arc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/basekick-labs/arc to 0.0.0-20260520170331-32a4091fb949 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j93g-rp6m-j32m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j93g-rp6m-j32m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j93g-rp6m-j32m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-j93g-rp6m-j32m in your dependencies?

O3 detects GHSA-j93g-rp6m-j32m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-j93g-rp6m-j32m

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Impact

Patches

Workarounds

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-j93g-rp6m-j32m in your dependencies?