Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48050 – Unauthenticated Info Disclosure & DoS via Exposed pprof Endpoints – Arc (Basekick-L

Be the first to know when new zero-days emerge:

Summary

CVE-2026-48050 is a missing-authentication vulnerability in Arc, the open-source SQL-native time-series database for telemetry maintained by Basekick-Labs. Arc registers Go’s net/http/pprof debug handlers and mistakenly includes the /debug/pprof/* path prefix in its list of publicly accessible routes, causing the authentication middleware to bypass token checks for these endpoints. As a result, an unauthenticated network attacker can retrieve sensitive runtime data and trigger CPU-exhaustion denial-of-service conditions, earning this issue a High severity rating.

Technical details

  • Root cause: Arc’s HTTP server mounts Go’s standard net/http/pprof package at /debug/pprof/* (via pprof.New() in internal/api/server.go), and this path prefix is included in the application’s PublicPrefixes list (defined in cmd/arc/main.go).
  • Trigger condition: The authentication middleware performs a prefix match against PublicPrefixes and short-circuits the token/authorization check whenever a request path matches, so any request beginning with /debug/pprof skips authentication entirely.
  • Attack vector: Remote and unauthenticated — an attacker who can reach the Arc HTTP/API port over the network can send simple GET requests (no credentials required) to endpoints such as /debug/pprof/heap, /debug/pprof/goroutine?debug=2, /debug/pprof/profile?seconds=N, or /debug/pprof/trace.
  • Impact:
    • Information disclosure: heap dumps and goroutine stacks can expose sensitive in-memory data, including cached authentication tokens, SQL query strings, and internal application state/code paths.
    • Denial of service: requesting extended CPU profiles or execution traces can consume server CPU and memory resources, degrading or disrupting service availability.

Affected software

  • Product: Arc (github.com/basekick-labs/arc)
  • Vulnerable versions: All releases prior to 26.06.1 (module versions before 0.0.0-20260520170331-32a4091fb949)
  • Fixed version: 26.06.1 and later

Severity

  • CVSS Score: 8.8 (High)
  • Vector (CVSS v4.0): 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
  • Reflects network attack vector, low attack complexity, no privileges or user interaction required, low confidentiality impact, and high availability impact.

Mitigation and recommended actions

  • Immediate: Upgrade Arc to version 26.06.1 or later, which removes the /debug/pprof prefix from the public route list and corrects the authentication bypass.
  • If patching is not immediately possible:
    • Block access to /debug/pprof* paths at the reverse proxy or load balancer in front of Arc.
    • Restrict network access to the Arc API port using firewall rules, limiting exposure to trusted internal hosts only.
    • Where feasible, disable the pprof handler registration in the deployed build until the upgrade can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge