Secuno
ENNL
Book demo

CVE-2026-65181

8.1 HIGHEPSS 0.56%
  1. Published9 Sept 2026

Description

Insufficient authorization of Data Source tables in Impala 2.7-4.5 allows a client with privileges to upload a file to remote storage and create a table to execute arbitrary Java code. Users are recommended to upgrade to version 4.5.2, which fixes this issue.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

Apache Impala≥ 2.7.0 < 4.5.2

Remediation

Fixed in
Apache Impala≥ 4.5.2

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-9295510.0
vm2 before 3.11.8 contains a sandbox escape vulnerability in NodeVM that allows…
CVE-2026-9295310.0
vm2 versions from 3.11.0 before 3.11.8 fail to protect host TypedArray and ArrayBuffer…
CVE-2026-9294610.0
vm2 before 3.11.7 contains a remote code execution vulnerability when require.external…
CVE-2026-929359.0
vm2 is a sandbox for running untrusted Node.js code. In versions >= 3.11.4 and <=…
CVE-2026-418708.8
Missing Authorization, Improper Control of Generation of Code ('Code Injection'),…
CVE-2026-592839.1
Applications that evaluate Spring Expression Language (SpEL) expressions using…

Frequently asked

Is CVE-2026-65181 being actively exploited?

CVE-2026-65181 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.56%.

How severe is CVE-2026-65181?

CVE-2026-65181 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.56% probability of exploitation.

Which products are affected by CVE-2026-65181?

Affected products include Apache Impala.

How do I fix CVE-2026-65181?

Upgrade affected software to a fixed version, for example Apache Impala 4.5.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-65181 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.