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.
CVE-2026-49360
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 50(Track)EG Risk 50/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 25, 2026
Advisory Details (3)
Auto-updated Aug 21, 2026advisory-database/vulns/recce/PYSEC-2026-3049.yaml at main · pypa/advisory-database · GitHub
https://github.com/pypa/advisory-database/tree/main/vulns/recce/PYSEC-2026-3049.yamlv1.50.0
Patch available: DataRecce/recce v1.50.0
https://github.com/DataRecce/recce/releases/tag/v1.50.0Unauthenticated SQL execution in Recce server allows local file read/write through DuckDB · Advisory · DataRecce/recce · GitHub
https://github.com/DataRecce/recce/security/advisories/GHSA-rh62-j648-g5qcVendor Advisories for CVE-2026-49360(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| recce | 0.1.0 ... 1.9.2 (188 versions) | 1.50.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 20:37 UTCEG score recompute
- 2026-08-25 19:37 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:55 UTCEG score recompute
- 2026-08-23 00:54 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:28 UTCEG score recompute
- 2026-08-21 23:04 UTCEG score recompute▲ 7.80
- 2026-08-21 23:04 UTCMITRE cvelistV5CVSS v3 → 7.8 · CVSS v4 → 7.8
- 2026-08-01 18:52 UTCEG score recompute
- 2026-07-26 13:02 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-02 22:07 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-49360?
When was CVE-2026-49360 disclosed?
Is CVE-2026-49360 actively exploited?
What is the CVSS score of CVE-2026-49360?
How do I remediate CVE-2026-49360?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49360
Is Your Infrastructure Affected by CVE-2026-49360?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.