CVE-2026-49360

{"id": "CVE-2026-49360", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-49360", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-25T18:34:58.371656Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.8, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/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": "NONE", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "LOW", "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": "DataRecce", "product": "recce", "versions": [{"status": "affected", "version": "< 1.50.0"}]}]}], "published": "2026-08-21T23:16:25.617", "references": [{"url": "https://github.com/DataRecce/recce/releases/tag/v1.50.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/DataRecce/recce/security/advisories/GHSA-rh62-j648-g5qc", "source": "security-advisories@github.com"}, {"url": "https://github.com/pypa/advisory-database/tree/main/vulns/recce/PYSEC-2026-3049.yaml", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-73"}]}], "descriptions": [{"lang": "en", "value": "Recce is a data-validation toolkit for enhanced dbt (data build tool) PR review. Prior to version 1.50.0, OSS server deployments that expose the server to an untrusted network without authentication are vulnerable to unauthenticated SQL execution through the query run API. When Recce is configured with a DuckDB-backed project, an attacker can use DuckDB filesystem primitives to read and write files accessible to the Recce server process. The impact depends on how Recce is deployed, but may include disclosure of local files, tampering with Recce/dbt artifacts, modification of browser-served static files leading to stored XSS, and modification of application files if those paths are writable. If Recce is run as root, file access occurs with root privileges inside that host or container. This issue has been patched in Recce `v1.50.0`. Users should upgrade to Recce `v1.50.0` or later. The patch restricts unsafe file read/write behavior for DuckDB-backed query execution and hardens the affected query path. Other warehouse adapters have also been reviewed for similar exposure. Users who cannot upgrade immediately should avoid exposing `recce server` to the public internet or any untrusted network. Recommended mitigations include enabling authentication or placing Recce behind an authenticated reverse proxy/VPN, running Recce as a non-root user, using a read-only application filesystem where possible, and ensuring that sensitive files or credentials are not available to the Recce process."}, {"lang": "es", "value": "Recce es un kit de herramientas de validaci\u00f3n de datos para una revisi\u00f3n mejorada de PR de dbt (herramienta de construcci\u00f3n de datos). Antes de la versi\u00f3n 1.50.0, los despliegues de servidor OSS que exponen el servidor a una red no confiable sin autenticaci\u00f3n son vulnerables a la ejecuci\u00f3n de SQL no autenticada a trav\u00e9s de la API de ejecuci\u00f3n de consultas. Cuyo Recce est\u00e1 configurado con un proyecto respaldado por DuckDB, un atacante puede usar primitivas del sistema de archivos de DuckDB para leer y escribir archivos accesibles al proceso del servidor de Recce. El impacto depende de c\u00f3mo se despliega Recce, pero puede incluir la divulgaci\u00f3n de archivos locales, la manipulaci\u00f3n de artefactos de Recce/dbt, la modificaci\u00f3n de archivos est\u00e1ticos servidos por el navegador que lleva a XSS almacenado, y la modificaci\u00f3n de archivos de aplicaci\u00f3n si esas rutas son escribibles. Si Recce se ejecuta como root, el acceso a archivos ocurre con privilegios de root dentro de ese host o contenedor. Este problema ha sido parcheado en Recce 'v1.50.0'. Los usuarios deben actualizar a Recce 'v1.50.0' o posterior. El parche restringe el comportamiento inseguro de lectura/escritura de archivos para la ejecuci\u00f3n de consultas respaldadas por DuckDB y refuerza la ruta de consulta afectada. Otros adaptadores de almac\u00e9n tambi\u00e9n han sido revisados en busca de una exposici\u00f3n similar. Los usuarios que no puedan actualizar de inmediato deben evitar exponer 'recce server' a la internet p\u00fablica o a cualquier red no confiable. Las mitigaciones recomendadas incluyen habilitar la autenticaci\u00f3n o colocar Recce detr\u00e1s de un proxy inverso/VPN autenticado, ejecutar Recce como un usuario no root, usar un sistema de archivos de aplicaci\u00f3n de solo lectura cuyo sea posible, y asegurar que los archivos o credenciales sensibles no est\u00e9n disponibles para el proceso de Recce."}], "lastModified": "2026-10-12T16:10:00.220", "sourceIdentifier": "security-advisories@github.com"}