CVE-2026-48105

{"id": "CVE-2026-48105", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-48105", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-24T18:44:53.970430Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "Basekick-Labs", "product": "arc", "versions": [{"status": "affected", "version": "< 2026.06.1"}]}]}], "published": "2026-08-21T23:16:25.220", "references": [{"url": "https://github.com/Basekick-Labs/arc/security/advisories/GHSA-f85q-mvg8-qf37", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-22"}, {"lang": "en", "value": "CWE-345"}, {"lang": "en", "value": "CWE-913"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Arc es una base de datos de series temporales abierta, nativa de SQL, para telemetr\u00eda. Antes de la versi\u00f3n 26.06.1, el FSM de Raft de Arc Enterprise ('internal/cluster/raft/fsm.go:applyRegisterFile') acepta rutas de archivo elegidas por el atacante en propuestas de registro de manifiesto sin validarlas contra el backend de almacenamiento configurado. La \u00fanica comprobaci\u00f3n es que la ruta no est\u00e9 vac\u00eda. No hay rechazo de recorrido de directorio padre ('..'), ninguna lista de permitidos de prefijos leg\u00edtimos, ninguna restricci\u00f3n de esquema ('s3://' vs local), y ning\u00fan l\u00edmite de longitud. Esto se ha corregido en la versi\u00f3n 2026.06.1. Hay algunas soluciones provisionales disponibles. Restrinja el acceso a la red del cl\u00faster a pares de confianza conocidos mediante reglas estrictas de cortafuegos, audite el manifiesto del cl\u00faster en busca de rutas inesperadas (cualquier ruta que no coincida con la ra\u00edz del backend de almacenamiento configurado es sospechosa), y/o deshabilite el modo de cl\u00faster hasta que la correcci\u00f3n est\u00e9 disponible."}], "lastModified": "2026-10-12T16:10:00.220", "sourceIdentifier": "security-advisories@github.com"}