CVE-2026-49360: CWE-73: External Control of File Name or Path in DataRecce recce
Recce versions prior to 1.50.0 have a vulnerability allowing unauthenticated SQL execution via the query run API on OSS server deployments exposed to untrusted networks without authentication. When configured with a DuckDB-backed project, this can lead to unauthorized file read/write access with the privileges of the Recce server process, potentially exposing or modifying local files, artifacts, static files, or application files. The vulnerability is patched in version 1.50.0. Users should upgrade or apply mitigations such as enabling authentication, restricting network exposure, running as non-root, and using read-only filesystems.
AI Analysis
Technical Summary
CVE-2026-49360 is an external control of file name or path vulnerability (CWE-73) in the DataRecce recce tool prior to version 1.50.0. The vulnerability arises when the OSS server is exposed to untrusted networks without authentication, allowing unauthenticated SQL execution through the query run API. Specifically, when Recce is configured with a DuckDB-backed project, an attacker can leverage DuckDB filesystem primitives to read and write files accessible to the Recce server process. This can lead to disclosure of local files, tampering with Recce/dbt artifacts, modification of browser-served static files causing stored XSS, and modification of application files if writable. If Recce runs as root, these file operations occur with root privileges. The issue is fixed in Recce version 1.50.0 by restricting unsafe file read/write behavior and hardening the query path. Other warehouse adapters have been reviewed for similar issues.
Potential Impact
The impact includes unauthorized disclosure of local files, modification of Recce or dbt artifacts, potential stored cross-site scripting via altered static files, and modification of application files if writable. If the Recce server runs with root privileges, the attacker gains root-level file access on the host or container. This can compromise confidentiality, integrity, and availability of the affected system and data.
Mitigation Recommendations
A fix is available in Recce version 1.50.0 and later. Users should upgrade to this version to remediate the vulnerability. For those unable to upgrade immediately, it is recommended to avoid exposing the Recce server to untrusted networks or the public internet. Additional mitigations include enabling authentication or placing Recce behind an authenticated reverse proxy or VPN, running Recce as a non-root user, using a read-only filesystem for the application where possible, and ensuring sensitive files or credentials are not accessible to the Recce process.
CVE-2026-49360: CWE-73: External Control of File Name or Path in DataRecce recce
Description
Recce versions prior to 1.50.0 have a vulnerability allowing unauthenticated SQL execution via the query run API on OSS server deployments exposed to untrusted networks without authentication. When configured with a DuckDB-backed project, this can lead to unauthorized file read/write access with the privileges of the Recce server process, potentially exposing or modifying local files, artifacts, static files, or application files. The vulnerability is patched in version 1.50.0. Users should upgrade or apply mitigations such as enabling authentication, restricting network exposure, running as non-root, and using read-only filesystems.
CVSS v4.0
Score 7.8high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-49360 is an external control of file name or path vulnerability (CWE-73) in the DataRecce recce tool prior to version 1.50.0. The vulnerability arises when the OSS server is exposed to untrusted networks without authentication, allowing unauthenticated SQL execution through the query run API. Specifically, when Recce is configured with a DuckDB-backed project, an attacker can leverage DuckDB filesystem primitives to read and write files accessible to the Recce server process. This can lead to disclosure of local files, tampering with Recce/dbt artifacts, modification of browser-served static files causing stored XSS, and modification of application files if writable. If Recce runs as root, these file operations occur with root privileges. The issue is fixed in Recce version 1.50.0 by restricting unsafe file read/write behavior and hardening the query path. Other warehouse adapters have been reviewed for similar issues.
Potential Impact
The impact includes unauthorized disclosure of local files, modification of Recce or dbt artifacts, potential stored cross-site scripting via altered static files, and modification of application files if writable. If the Recce server runs with root privileges, the attacker gains root-level file access on the host or container. This can compromise confidentiality, integrity, and availability of the affected system and data.
Mitigation Recommendations
A fix is available in Recce version 1.50.0 and later. Users should upgrade to this version to remediate the vulnerability. For those unable to upgrade immediately, it is recommended to avoid exposing the Recce server to untrusted networks or the public internet. Additional mitigations include enabling authentication or placing Recce behind an authenticated reverse proxy or VPN, running Recce as a non-root user, using a read-only filesystem for the application where possible, and ensuring sensitive files or credentials are not accessible to the Recce process.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rh62-j648-g5qc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-49360"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46ecad27e9c7971943b87d
Added to database: 07/02/2026, 22:56:45 UTC
Last enriched: 09/12/2026, 21:31:40 UTC
Last updated: 09/14/2026, 22:01:34 UTC
Views: 141
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.