# CVE-2026-48105: Path traversal in arc

> Attackers can exploit path traversal in Arc Enterprise cluster FSM to register arbitrary files, potentially enabling cluster-wide compromise or data access.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-f85q-mvg8-qf37

## What is CVE-2026-48105?

CVE-2026-48105 is a high-severity path traversal vulnerability in Basekick-Labs arc, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's Raft FSM (`internal/cluster/raft/fsm.go:applyRegisterFile`) accepts attacker-chosen file paths in manifest-registration proposals without validating them against the configured storage backend. The only check is that the path is non-empty. There is no parent-traversal (`..`) rejection, no allowlist of legitimate prefixes, no scheme restriction (`s3://` vs local), and no length bound. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit the cluster manifest for unexpected paths (any path not matching the configured storage backend root is suspect), and/or disable cluster mode until the fix is available.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources), CWE-345 (Insufficient Verification of Data Authenticity), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2026-48105 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48105 is a high-severity path traversal vulnerability in Basekick-Labs arc, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48105 in the wild and no public exploit code.

Affected product: Basekick-Labs arc. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-48105/ (Markdown: https://insights.sbomify.com/CVE-2026-48105/index.md)
```

## Sources

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

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