Description
Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's cluster replication receiver at `internal/cluster/replication/receiver.go` validates only the wire-format envelope (length, opcode) of inbound messages. The `MsgReplicateSync` payload itself is accepted without any application-layer authentication — no HMAC, no signature, no per-message nonce. The replication stream is protected at the transport layer by TLS / mTLS, but there is no protection against application-layer message tampering or replay once a peer is on the cluster network. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit replication logs for unexpected `MsgReplicateSync` traffic, and/or disable cluster mode until the fix is available.
Published: 2026-08-21
Score: 8.3 High
EPSS: < 1% Very Low
KEV: No
Impact: Data Integrity Compromise
Action: Immediate Patch
AI Analysis

Impact

Arc Enterprise, an open SQL‑native time‑series database, processes replicated cluster messages without application‑layer authentication. The MsgReplicateSync payload is accepted as long as the message envelope is valid, meaning an attacker can inject arbitrary data into the database once a peer is part of the cluster network. This vulnerability does not directly allow remote code execution, but it enables the modification or corruption of stored telemetry data, undermining the reliability of analysis and potential downstream decisions.

Affected Systems

The vulnerability affects Basekick‑Labs’ Arc Enterprise product in all versions released before 26.06.1. Users running earlier releases that enable cluster replication are susceptible; any node that accepts MsgReplicateSync messages without further authentication is impacted. Upgrading to 26.06.1 or later removes the flaw.

Risk and Exploitability

The CVSS score of 8.3 indicates a high severity issue. Exploit probability data (EPSS) is not available, but the flaw is listed in no KEV catalog, suggesting it has not yet been widely leveraged. The attack vector is likely limited to peers that already have TLS/mTLS trust within the cluster, so an adversary must either compromise a legitimate cluster member or sit on the same network to inject messages. Once in the cluster network, the attacker could replay or tamper with data, and the lack of per‑message defenses means replay is also feasible. Given the high CVSS and the critical nature of telemetry data, the risk remains substantial.

Generated by OpenCVE AI on August 22, 2026 at 00:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Arc Enterprise to version 26.06.1 or later to apply the fix that enforces application‑layer authentication for MsgReplicateSync messages.
  • Configure firewall or network segmentation rules to allow cluster traffic only between known‑trusted peers, reducing the number of nodes that can send replication messages.
  • Audit replication logs for unexpected or malformed MsgReplicateSync traffic and consider disabling cluster mode temporarily if a patch cannot be applied promptly.

Generated by OpenCVE AI on August 22, 2026 at 00:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sun, 23 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Basekick-labs
Basekick-labs arc
Vendors & Products Basekick-labs
Basekick-labs arc

Fri, 21 Aug 2026 23:00:00 +0000

Type Values Removed Values Added
Description Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's cluster replication receiver at `internal/cluster/replication/receiver.go` validates only the wire-format envelope (length, opcode) of inbound messages. The `MsgReplicateSync` payload itself is accepted without any application-layer authentication — no HMAC, no signature, no per-message nonce. The replication stream is protected at the transport layer by TLS / mTLS, but there is no protection against application-layer message tampering or replay once a peer is on the cluster network. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit replication logs for unexpected `MsgReplicateSync` traffic, and/or disable cluster mode until the fix is available.
Title Arc Enterprise cluster replication accepts unauthenticated MsgReplicateSync messages, enabling cluster-wide data injection from any TLS-trusted peer
Weaknesses CWE-306
CWE-345
CWE-924
References
Metrics cvssV4_0

{'score': 8.3, 'vector': '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'}


Subscriptions

Basekick-labs Arc
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-26T17:47:20.195Z

Reserved: 2026-05-20T18:46:58.285Z

Link: CVE-2026-48106

cve-icon Vulnrichment

Updated: 2026-08-26T17:47:16.245Z

cve-icon NVD

Status : Deferred

Published: 2026-08-21T23:16:25.360

Modified: 2026-09-09T21:06:39.057

Link: CVE-2026-48106

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-23T16:40:14Z

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-924

    Improper Enforcement of Message Integrity During Transmission in a Communication Channel