What is CVE-2026-49360?

CVE-2026-49360 is a high-severity security vulnerability in recce (pip), affecting versions <= 1.49.0. It is fixed in 1.50.0.

Which versions of recce are affected by CVE-2026-49360?

recce (pip) versions <= 1.49.0 is affected.

Is there a fix for CVE-2026-49360?

Yes. CVE-2026-49360 is fixed in 1.50.0. Upgrade to this version or later.

Is CVE-2026-49360 exploitable, and should I be worried?

Whether CVE-2026-49360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-49360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-49360?

Upgrade recce to 1.50.0 or later.

CVE-2026-49360 in recce

Q: Which versions of recce are affected by CVE-2026-49360?

recce (pip) versions <= 1.49.0 is affected.

Q: Is there a fix for CVE-2026-49360?

Yes. CVE-2026-49360 is fixed in 1.50.0. Upgrade to this version or later.

Q: Is CVE-2026-49360 exploitable, and should I be worried?

Whether CVE-2026-49360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-49360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-49360?

Upgrade recce to 1.50.0 or later.

Summary

Recce server has unauthenticated SQL execution that allows local file read/write through DuckDB

Credits

Thanks to Sitampan (@hxcbtc) for responsibly reporting this issue.

Workarounds

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.

Impact

Recce 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.

Affected versions

recce (<= 1.49.0)

Security releases

recce → 1.50.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-49360? CVE-2026-49360 is a high-severity security vulnerability in recce (pip), affecting versions <= 1.49.0. It is fixed in 1.50.0.
Which versions of recce are affected by CVE-2026-49360? recce (pip) versions <= 1.49.0 is affected.
Is there a fix for CVE-2026-49360? Yes. CVE-2026-49360 is fixed in 1.50.0. Upgrade to this version or later.
Is CVE-2026-49360 exploitable, and should I be worried? Whether CVE-2026-49360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-49360 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-49360? Upgrade recce to 1.50.0 or later.