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

> Unauthenticated access to Arc database debug endpoints allows attackers to leak runtime state and cause denial of service via CPU exhaustion.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-j93g-rp6m-j32m, GO-2026-5457

## What is CVE-2026-48050?

CVE-2026-48050 is a high-severity vulnerability in Basekick-Labs arc, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arc is an open, SQL-native time-series database for telemetry. Versions prior to 26.06.1 register 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. Version 26.06.1 contains a patch. Some workarounds are available. 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, and/or patch the running build: comment out `app.Use(pprof.New())` in `internal/api/server.go` and rebuild.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-48050?

3 open source packages ship an affected version, including github.com/basekick-labs/arc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/basekick-labs/arc` | Go | All versions | 0.0.0-20260520170331-32a4091fb949 |
| `github.com/basekick-labs/arc` | Go | All versions | 0.0.0-20260520170331-32a4091fb949 |
| `github.com/basekick-labs/arc` | Go | All versions | 0.0.0-20260520170331-32a4091fb949 |

## How do I fix CVE-2026-48050?

Upgrade github.com/basekick-labs/arc to 0.0.0-20260520170331-32a4091fb949 or later.

## Is CVE-2026-48050 being exploited?

There is no known exploitation of CVE-2026-48050 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48050 and fix it if it is affected.

What it is: CVE-2026-48050 is a high-severity vulnerability in Basekick-Labs arc, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48050 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/basekick-labs/arc (Go): affected all versions; fixed in 0.0.0-20260520170331-32a4091fb949
- github.com/basekick-labs/arc (Go): affected all versions; fixed in 0.0.0-20260520170331-32a4091fb949
- github.com/basekick-labs/arc (Go): affected all versions; fixed in 0.0.0-20260520170331-32a4091fb949

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48050/ (Markdown: https://insights.sbomify.com/CVE-2026-48050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48050
- OSV: https://osv.dev/vulnerability/CVE-2026-48050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48050/
Summaries are generated and may contain mistakes; the official description above is the record.