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
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1% (64th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-64204 (ENISA EUVD) · GHSA-rh62-j648-g5qc (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 51EG Risk 51/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation1.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.1%
- EPSS %ILE
- 64th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 2, 2026
Last Modified
October 12, 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.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | recce @ 1.50.0 (fixes <= 1.49.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| recce | 0.1.0 ... 1.9.2 (188 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 07:46 UTCGHSA enrichmentGHSA-rh62-j648-g5qc · GitHub severity HIGH
- 2026-11-01 07:46 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-29 20:18 UTCEG score recompute
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-25 14:22 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-22 11:55 UTCEG score recompute
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-20 09:45 UTCEG score recompute
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-18 03:34 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
Show 65 moreShow fewer
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-12 16:00 UTCEG score recompute
- 2026-10-11 19:43 UTCEG score recompute
- 2026-10-11 16:57 UTCEG score recompute
- 2026-10-11 14:21 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-23 06:38 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-18 06:14 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-14 00:15 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-13 08:59 UTCEG score recompute
- 2026-09-12 14:15 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-09 22:58 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-06 14:19 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-05 23:51 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-30 23:51 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-30 11:22 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-27 22:14 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-25 20:37 UTCEG score recompute
- 2026-08-25 19:37 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-24 20:55 UTCEG score recompute
- 2026-08-23 00:54 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-21 23:28 UTCEG score recompute
- 2026-08-21 23:04 UTCEG score recomputeFirst assessed: 7.8 HIGH
- 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
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-49360?
When was the CVE record for CVE-2026-49360 published?
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.