{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "0"
                  },
                  {
                    "fixed": "26.06.1"
                  }
                ],
                "source": "DESCRIPTION"
              }
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8038f6f80f77bb48dbaa220e7415957be3988eff"
            }
          ],
          "repo": "https://github.com/basekick-labs/arc",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-f85q-mvg8-qf37"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-22",
      "CWE-345",
      "CWE-913"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48105.json",
    "unresolved_ranges": [
      {
        "extracted_events": [
          {
            "range": [
              {
                "fixed": "2026.06.1"
              }
            ],
            "source": "AFFECTED_FIELD",
            "strategy": "StringRangeExpression"
          }
        ]
      },
      {
        "extracted_events": [
          {
            "range": [
              {
                "fixed": "2026.06.1"
              }
            ],
            "source": "DESCRIPTION"
          }
        ]
      }
    ]
  },
  "details": "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.",
  "id": "CVE-2026-48105",
  "modified": "2026-10-28T02:30:25.871835718Z",
  "published": "2026-08-21T22:47:13.993Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/Basekick-Labs/arc/security/advisories/GHSA-f85q-mvg8-qf37"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48105.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48105"
    }
  ],
  "schema_version": "1.9.2",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Arc Enterprise cluster FSM applyRegisterFile accepts arbitrary file paths without validation, enabling cluster-wide path-traversal worm primitive"
}