CVE-2026-54048

Analyzed Analyzed - Analysis Complete

Remote Code Execution via Malicious Avro Schema URL in Apache Impala

Publication date: 2026-09-09

Last updated on: 2026-09-10

Assigner: Apache Software Foundation

Description

Specifying tblproperties('avro.schema.url'=' http://...' ) or with a 'file:///' URI on a table in Impala 2.0.0 to 4.5.1 on all platforms allows an attacker to trigger a GET request to internal endpoints they may not have access to but that Impala does and the response my be exposed via parsing error messages. Users are recommended to upgrade to version 4.5.2, which fixes this issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-09

Last Modified

2026-09-10

Generated

2026-09-29

AI Q&A

2026-09-09

EPSS Evaluated

2026-09-27

NVD

CVE-2026-54048

EUVD

EUVD-2026-74795

Affected Vendors & Products

Vendor	Product	Version / Range
apache	impala	From 2.7.0 (inc) to 4.5.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	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.

Attack-Flow Graph

Executive Summary

This is a Server-Side Request Forgery (SSRF) flaw in Apache Impala versions 2.0.0 to 4.5.1. Attackers can specify a malicious 'avro.schema.url' parameter with a URL or 'file:///' URI when creating a table. This forces Impala to make a GET request to internal endpoints the attacker cannot access directly, potentially exposing sensitive data through error messages.

Detection Guidance

Check Impala versions between 2.0.0 and 4.5.1. Inspect logs for GET requests triggered by tblproperties with avro.schema.url or file:// URIs. Monitor network traffic for unexpected internal endpoint connections.

Impact Analysis

An attacker could exploit this to access internal services or data that Impala can reach but they cannot. Sensitive information might be leaked via parsing error messages. The impact depends on what internal endpoints Impala can access and what data is exposed.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. If exploited, it may result in data breaches, triggering compliance violations and potential fines depending on the exposed data.

Mitigation Strategies

Upgrade Impala to version 4.5.2 or later immediately. Disable or restrict access to tblproperties modifications that allow avro.schema.url or file:// URIs. Review and audit existing configurations for suspicious patterns.

Hi! I’m here to help you understand CVE-2026-54048. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70