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.
CVE-2026-47735
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
June 8, 2026
Last Modified
August 25, 2026
Advisory Details (4)
Auto-updated Aug 21, 2026Arc 26.06.1
Patch available: Basekick-Labs/arc v26.06.1
https://github.com/Basekick-Labs/arc/releases/tag/v26.06.1commit 91bdc29d1a02 (Basekick-Labs/arc)
Fix landed in Basekick-Labs/arc commit 91bdc29d1a02 — awaiting tagged release
https://github.com/Basekick-Labs/arc/commit/91bdc29d1a02178ccf8c66375eccf85203108dfbfix(security): sandbox DuckDB user queries via enable_external_access=false + allowed_directories
Fix merged in Basekick-Labs/arc PR #442 on 2026-05-20 — awaiting tagged release
https://github.com/Basekick-Labs/arc/pull/442Authenticated arbitrary local-file read via DuckDB I/O functions bypasses RBAC table-level checks · Advisory · Basekick-Labs/arc · GitHub
Affected: 2026.06.1 (PR
https://github.com/Basekick-Labs/arc/security/advisories/GHSA-p2j4-c4g6-rpf5Vendor Advisories for CVE-2026-47735(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/basekick-labs/arc | — | 0.0.0-20260520141557-91bdc29d1a02 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 14:21 UTCEG score recompute
- 2026-08-25 14:00 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 00:56 UTCEG score recompute
- 2026-08-23 11:23 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:28 UTCEG score recompute
- 2026-08-21 22:54 UTCEG score recompute▲ 7.10
- 2026-08-21 22:54 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
- 2026-07-31 04:43 UTCEG score recompute
- 2026-07-26 21:32 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-08 23:56 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-918 · CWE-200
Frequently asked(5)
What is CVE-2026-47735?
When was CVE-2026-47735 disclosed?
Is CVE-2026-47735 actively exploited?
What is the CVSS score of CVE-2026-47735?
How do I remediate CVE-2026-47735?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47735
Is Your Infrastructure Affected by CVE-2026-47735?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.