# CVE-2026-96443: Apache Doris: JDBC driver URL validation bypass leads to remote code execution

> A privileged user can achieve remote code execution on the Frontend by bypassing JDBC driver URL validation in Apache Doris.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-h927-w38j-3g6x

## What is CVE-2026-96443?

CVE-2026-96443 is a medium-severity code injection vulnerability in Apache Doris, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient validation of the JDBC driver URL in Apache Doris allows a privileged user to achieve remote code execution on the FE.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

No fix has been published for CVE-2026-96443 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96443 being exploited?

There is no known exploitation of CVE-2026-96443 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96443 is a medium-severity code injection vulnerability in Apache Doris, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96443 in the wild and no public exploit code.

Affected product: Apache Doris. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-96443/ (Markdown: https://insights.sbomify.com/CVE-2026-96443/index.md)
```

## Sources

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

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