CVE-2026-54048: Apache Software Foundation Apache Impala · Server-Side Request Forgery (SSRF)
Affects Apache Software Foundation Apache ImpalaSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 4.5.2 : update Apache Software Foundation Apache Impala when convenient.
Data as of 10/25/2026, 09:04:00 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Impala | Affected
| Fixed in– |
Mavenorg.apache.impala/impalapkg:maven/org.apache.impala/impalaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache Impala to version 4.5.2 or later, which contains the official fix for this SSRF vulnerability. No other mitigation is indicated by the vendor advisory.
Description
Apache Impala versions 2.0.0 through 4.5.1 contain a server-side request forgery (SSRF) vulnerability. This flaw allows an attacker to specify a table property with an avro.schema.url pointing to an HTTP or file URI, causing Impala to issue GET requests to internal endpoints. The responses may be exposed through parsing error messages. The issue is fixed in version 4.5.2.
Impact
An attacker without privileges can trigger Impala to make HTTP GET requests to internal endpoints that the attacker may not have direct access to. The responses to these requests may be exposed through error message parsing, potentially leaking sensitive internal information. The vulnerability does not allow integrity or availability impact, only limited confidentiality exposure.
Weaknesses
- CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.