# CVE-2026-3293: snowflakedb snowflake-jdbc JDBC URL SdkProxyRoutePlanner.java SdkProxyRoutePlanner redos

> A local attacker can cause denial of service in the Snowflake JDBC library by exploiting inefficient regular expression complexity in the proxy route planner.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-gx6c-pv62-9mcf, RHLW-2026-e9343e476d7f9acf

## What is CVE-2026-3293?

CVE-2026-3293 is a medium-severity denial of service vulnerability in snowflakedb snowflake-jdbc, published on 27 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in snowflakedb snowflake-jdbc up to 4.0.1. Impacted is the function SdkProxyRoutePlanner of the file src/main/java/net/snowflake/client/internal/core/SdkProxyRoutePlanner.java of the component JDBC URL Handler. Executing a manipulation of the argument nonProxyHosts can lead to inefficient regular expression complexity. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 5fb0a8a318a2ed87f4022a1f56e742424ba94052. A patch should be applied to remediate this issue.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-3293?

2 open source packages ship an affected version, including net.snowflake:snowflake-jdbc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.snowflake:snowflake-jdbc` | Maven | All versions to 4.0.1 | None |
| `net.snowflake:snowflake-jdbc` | Maven | All versions to 4.0.1 | None |

Products: Snowflake Snowflake Jdbc.

## How do I fix CVE-2026-3293?

Apply the vendor's patch.

## Is CVE-2026-3293 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3293 exists.

## Other vulnerabilities in snowflakedb snowflake-jdbc

- [CVE-2025-24789](https://insights.sbomify.com/CVE-2025-24789/): Snowflake JDBC allows an untrusted search path on Windows (high 7.8)
- [CVE-2023-30535](https://insights.sbomify.com/CVE-2023-30535/): Snowflake JDBC vulnerable to command injection via SSO URL authentication (high 7.3)
- [CVE-2024-43382](https://insights.sbomify.com/CVE-2024-43382/): Snowflake JDBC Security Advisory (medium 5.9)
- [CVE-2025-24790](https://insights.sbomify.com/CVE-2025-24790/): Snowflake JDBC uses insecure temporary credential cache file permissions (medium 4.4)
- [CVE-2025-27496](https://insights.sbomify.com/CVE-2025-27496/): Snowflake JDBC Driver client-side encryption key in DEBUG logs (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3293 and fix it if it is affected.

What it is: CVE-2026-3293 is a medium-severity denial of service vulnerability in snowflakedb snowflake-jdbc, published on 27 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3293 exists.

Affected packages and fixed versions:
- net.snowflake:snowflake-jdbc (Maven): affected all versions up to 4.0.1; no fix listed
- net.snowflake:snowflake-jdbc (Maven): affected all versions up to 4.0.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3293/ (Markdown: https://insights.sbomify.com/CVE-2026-3293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3293
- OSV: https://osv.dev/vulnerability/CVE-2026-3293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3293/
Summaries are generated and may contain mistakes; the official description above is the record.