# CVE-2026-47735: Arc has an authenticated arbitrary local-file read via DuckDB I/O functions that bypasses RBAC table-level checks

> Authenticated users can read arbitrary local files by bypassing SQL validation and RBAC checks using unblocked DuckDB I/O functions.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-p2j4-c4g6-rpf5, GO-2026-5523

## What is CVE-2026-47735?

CVE-2026-47735 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's user-SQL validator (`internal/api/query.go:ValidateSQLRequest`) blocked only `read_parquet(` and `arc_partition_agg(` via regex denylist. The broader DuckDB I/O function family — `read_csv_auto`, `read_csv`, `read_json`, `read_json_auto`, `read_text`, `read_blob`, `glob`, `parquet_metadata`, `parquet_schema`, `read_xlsx`, etc. — was not blocked. RBAC table-reference extraction inspected only `FROM`/`JOIN` clauses, so scalar table functions in the `SELECT` list slipped past both layers. This is fixed in 2026.06.1 via a structural sandbox at the DuckDB layer. After lockdown, DuckDB refuses to open any file outside the allowlist and refuses further `INSTALL`/`LOAD`. Already-loaded extensions remain callable. Some workarounds are available. Restrict API access to known-trusted networks via firewall rules or, as a temporary mitigation, add `read_csv*`/`read_json*`/`glob` etc. to `dangerousSQLPattern` in `internal/api/query.go`.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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-20260520141557-91bdc29d1a02 |
| `github.com/basekick-labs/arc` | Go | All versions | 0.0.0-20260520141557-91bdc29d1a02 |
| `github.com/basekick-labs/arc` | Go | All versions | 0.0.0-20260520141557-91bdc29d1a02 |

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

Upgrade github.com/basekick-labs/arc to 0.0.0-20260520141557-91bdc29d1a02 or later.

## Is CVE-2026-47735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47735 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-47735 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-20260520141557-91bdc29d1a02
- github.com/basekick-labs/arc (Go): affected all versions; fixed in 0.0.0-20260520141557-91bdc29d1a02
- github.com/basekick-labs/arc (Go): affected all versions; fixed in 0.0.0-20260520141557-91bdc29d1a02

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

## Sources

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

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