CVE-2026-49360: Recce Recce Server Has Unauthenticated SQL Vulnerability
HIGHCVE-2026-49360 is a HIGH recce server has unauthenticated sql vulnerability (CWE-73: External Control of File Name or Path) affecting Recce libraries in the PyPI ecosystem. The issue involves recce server has unauthenticated sql execution that allows local file read/write through duckdb. Remediation is available by upgrading affected packages to version 1.50.0.
CVE-2026-49360 at a Glance
How to Fix CVE-2026-49360
To remediate this vulnerability, upgrade all affected Recce dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install recce>=1.50.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show recce
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-49360, inspect your installed packages using pip:
pip show recce
Analyze the terminal output to locate any version of Recce in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.50.0), your application is affected.
Note: The pip show recce command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In Recce, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-49360 Affected Recce Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
recce
|
PyPI |
< 1.50.0
|
1.50.0
|
References
Frequently Asked Questions
What is CVE-2026-49360?
Which Recce versions are affected?
What version fixes CVE-2026-49360?
Is recce affected?
What CWE is associated with CVE-2026-49360?
How can I check PyPI dependencies for CVE-2026-49360?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rh62-j648-g5qc",
"modified" : "2026-07-02T21:14:38Z",
"published" : "2026-07-02T21:14:38Z",
"aliases" : [ "CVE-2026-49360" ],
"summary" : "Recce server has unauthenticated SQL execution that allows local file read/write through DuckDB",
"details" : "### Impact\nRecce OSS server deployments that expose the server to an untrusted network without authentication are vulnerable to unauthenticated SQL execution through the query run API.\n\nWhen 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.\n\n### Patches\nThis issue has been patched in Recce `v1.50.0`. Users should upgrade to Recce `v1.50.0` or later.\n\nThe 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.\n\n### Credits\nThanks to Sitampan ([@hxcbtc](https://x.com/hxcbtc)) for responsibly reporting this issue.\n\n### Workarounds\nUsers who cannot upgrade immediately should avoid exposing `recce server` to the public internet or any untrusted network.\n\nRecommended 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.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "recce"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.50.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.49.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/DataRecce/recce/security/advisories/GHSA-rh62-j648-g5qc"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/DataRecce/recce"
}, {
"type" : "WEB",
"url" : "https://github.com/DataRecce/recce/releases/tag/v1.50.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-73" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-02T21:14:38Z",
"nvd_published_at" : null
}
}