Prior to version 1.50.0, the Recce data-validation toolkit permits an unauthenticated user to execute arbitrary SQL through the query run API. When the project is configured with a DuckDB backend, the attacker can exploit DuckDB’s filesystem primitives to read or write any file accessible to the Recce server process. This ability enables disclosure of sensitive local files, corruption of Recce or dbt artifacts, injection of stored XSS by modifying browser‑served static files, and alteration of application code if write paths are writable, especially when Recce runs with root privileges, elevating the impact to full host compromise.

DataRecce’s Recce OSS server deployments that are exposed to an untrusted network without authentication, using a DuckDB‑backed project, in any version older than 1.50.0. The vulnerability is specific to the Recce server component of DataRecce’s Recce product.

The CVSS base score of 7.8 reflects a high‑severity flaw and there is no EPSS score available, indicating that the exploitation probability is uncertain but not negligible. The flaw is not listed in CISA’s KEV catalog. The most likely attack vector is the publicly reachable query run endpoint; because authentication is missing, an attacker can easily trigger the vulnerability over the network. The combination of elevated file system access, potential root execution, and lack of authentication makes this a high‑risk exposure for systems that expose Recce to untrusted networks.