CVE-2021-26919

What it is

Apache Druid allows users to read data from other database systems using JDBC. This functionality is to allow trusted users with the proper permissions to set up lookups or submit ingestion tasks. The MySQL JDBC driver supports certain properties, which, if left unmitigated, can allow an attacker to execute arbitrary code from a hacker-controlled malicious MySQL server within Druid server processes. This issue was addressed in Apache Druid 0.20.2

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.

Exploit odds

35.2% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-02-09 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2021-03-30 08:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 03:44 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 35.2% in the next 30 days (EPSS).
• Severity: 8.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-03-30 08:15 UTC

Last modified

2026-06-17 03:44 UTC

Exploit probability

35.2% · EPSS, next 30 days

Record status

Modified

Affected

• Apache Druid < 0.20.2

Attack profile CVSS 3.1 · 8.8

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-26919.md and follow it. Check whether this project is affected by CVE-2021-26919. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge