Skip to main content

Apache Doris CVE-2026-31377

| EUVDEUVD-2026-85172 HIGH
Improper Authentication (CWE-287)
2026-09-23 apache GHSA-6cx7-4x8x-cqpx
7.5
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach FE meta service endpoint
  2. Delivery
    Send request with spoofed node information
  3. Exploit
    Bypass client-supplied-info authentication
  4. Execution
    Access internal FE metadata interfaces
  5. Impact
    Exfiltrate sensitive cluster information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires network reachability to the Apache Doris FE meta service internal metadata endpoints, and the flaw is explicitly gated by deployment: it is exploitable only 'under certain network configurations' where those FE interfaces are reachable by the attacker. The root cause is that the affected endpoints authenticate callers using client-supplied node information (header trust) rather than authenticating the requesting party, so an unauthenticated remote attacker (PR:N/UI:N) who reaches the endpoint can spoof trusted-node data. Limiting factors: only Apache Doris 2.0.0-2.1.*, 3.0.0-3.1.*, 4.0.0 before 4.0.8, and 4.1.0 before 4.1.4 are affected (1.2.x and earlier are not), and network segmentation that keeps FE meta interfaces off attacker-reachable networks prevents exploitation. Impact is confidentiality-only (metadata/cluster information disclosure).

Impact

This is a genuine but conditional priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) reports a network-reachable, low-complexity, unauthenticated flaw with high confidentiality impact and no integrity or availability impact - consistent with metadata/information disclosure rather than takeover. The CWE-287 improper-authentication classification is accurate: authentication is based on client-supplied node information (a header-trust design), so an attacker who can reach the FE meta endpoints can impersonate a trusted node. The key tempering signal is in the description itself: exploitation only works 'under certain network configurations,' which argues the real-world attack complexity is higher than the AC:L in the vector suggests - deployments that keep FE meta interfaces on a private/segmented network are not exposed. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or automatable exploitation; the only source is the Apache mailing-list advisory. Net: a real, patch-worthy confidentiality issue for internet- or broadly-network-exposed Doris FE nodes, but not a drop-everything item absent exposure of the meta service. Note the C:H/I:N/A:N shape means this leaks cluster information, it does not directly grant code execution or data modification.

Exploit ScenarioDerived

An attacker who can reach an Apache Doris FE node's meta service endpoints (e.g., on a flat network or an exposed management interface) sends crafted requests supplying node information that the server trusts for authentication, without proving it is a legitimate cluster node. Because the endpoints authenticate the caller solely on that client-supplied data, the attacker bypasses access control and reads internal FE metadata interfaces, harvesting sensitive cluster information. No public exploit code was identified at time of analysis; exploitation depends on the FE meta service being network-reachable to the attacker.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 23, 2026

Unauthenticated remote attackers can reach internal Apache Doris Frontend (FE) metadata service endpoints in affected 2.0.x through 4.1.x releases and read sensitive cluster information, because those endpoints authenticate callers using client-supplied node information rather than verifying the requesting party (CWE-287, header trust). Exploitation is gated by deployment: it only succeeds 'under certain network configurations' where the FE meta interfaces are reachable by the attacker, so clusters with the FE meta service kept off attacker-reachable networks are not exposed. The vulnerability is rated CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) with confidentiality-only impact - no integrity or availability effect - and no public exploit has been identified at time of analysis; there is no CISA KEV listing. Vendor-released patches exist in Apache Doris 4.0.8 and 4.1.4.

RemediationAI

Upgrade to a fixed release - Apache Doris 4.0.8 for the 4.0.x line or 4.1.4 for the 4.1.x line, the versions named in the vendor advisory (https://lists.apache.org/thread/rf4ocqmzxvnwnxpsooj2lkzjl68b1m9q) - as the primary and complete fix; no configuration-only equivalent is documented. Because exploitation depends entirely on an attacker being able to reach the FE meta service endpoints, the most effective compensating control when an immediate upgrade is not possible is strict network segmentation: place the FE metadata/RPC interfaces on a trusted, cluster-internal network and enforce firewall rules or security groups that permit them only from legitimate FE/BE node addresses, blocking all other sources, including otherwise trusted corporate or management networks that could be compromised. The trade-off is operational - multi-cluster federation, cross-VPC deployments, and remote administration/monitoring tooling that relies on direct FE meta access will break and must be re-routed through a bastion or VPN. Additionally, treat any pre-4.0.8/4.1.4 cluster whose FE meta service was internet-exposed or reachable from untrusted segments as potentially inspected: review FE logs for requests to metadata endpoints originating from unexpected source addresses, and rotate any cluster credentials or secrets that may have been disclosed through exposed metadata. Rolling back to 1.2.x is not a practical mitigation since it means abandoning years of features and data-format compatibility; upgrading remains the recommended path.

Affected VersionsENISA

Apache Doris 4.1.0 <4.1.4
Apache Doris 2.0.0 <4.0.8

Affected Packages

euvd apache_doris fix: 4.0.8, 4.1.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache Doris is an MPP-based real-time analytical (OLAP) database whose Frontend (FE) node is a Java service responsible for metadata management, query planning and cluster coordination, while Backend (BE) nodes store and execute data. The FE meta service exposes internal metadata interfaces used for cluster state exchange and administration; per the advisory, these endpoints relied on client-supplied node information - effectively header/field trust - to decide whether a caller was a legitimate cluster node, instead of performing actual authentication of the requesting party. That is the classic CWE-287 Improper Authentication pattern in which a trusted-network assumption is encoded into application logic, so any party that can reach the endpoint and spoof the expected node metadata is treated as trusted. The CPE record (cpe:2.3:a:apache_software_foundation:apache_doris:*:*:*:*:*:*:*:*) is a wildcard covering the product family rather than a version-specific binding, so version scoping must come from the advisory text: 2.0.0 through 2.0.*, 2.1.0 through 2.1.*, 3.0.0 through 3.0.*, 3.1.0 through 3.1.*, 4.0.0 before 4.0.8, and 4.1.0 before 4.1.4. The 1.2.x line and earlier are explicitly not affected because the vulnerable header-trust behavior was not present, indicating the weakness is a regression or design addition introduced in the 2.0 development cycle. Impact is confidentiality-only: exposure of internal FE metadata and cluster information, not code execution or data modification.

Know when Apache Doris gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network access to FE meta endpoints trusting client-supplied node info (PR:N/AV:N); confidentiality-only cluster-metadata disclosure (C:H/I:N/A:N); AC:L kept per vendor though 'certain network configs' could justify AC:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Sep 23, 2026 - 10:01 EUVD
CVE Published
Sep 23, 2026 - 09:04 cve.org
HIGH 7.5

DescriptionCVE.org

An Improper Authentication vulnerability in the Apache Doris Frontend (FE) meta service allows an unauthenticated remote attacker to access internal metadata service endpoints.

The affected endpoints relied on client-supplied node information for authentication without providing sufficient authentication of the requesting party. Under certain network configurations, a remote attacker may be able to bypass the intended access control and access internal FE metadata interfaces, potentially exposing sensitive cluster information.

This issue affects Apache Doris: from 2.0.0 through 2.0.*, from 2.1.0 through 2.1.*, from 3.0.0 through 3.0.*, from 3.1.0 through 3.1.*, from 4.0.0 before 4.0.8, and from 4.1.0 before 4.1.4. Versions 1.2.x and earlier are not affected by this header-trust vulnerability.

Users are recommended to upgrade to a fixed release (4.0.8 or 4.1.4), which fixes the issue.

Executive ViewAI

Why It Matters

Apache Doris clusters running releases 2.0.x through 4.1.x may expose internal cluster metadata to anyone who can route traffic to the Frontend (FE) metadata service, with no credentials required. Because the affected code trusts identity information supplied by the caller rather than verifying it, an attacker positioned on a reachable network path could enumerate cluster topology and configuration detail that is useful for planning deeper intrusion. Only organizations whose FE metadata interfaces are exposed beyond trusted network boundaries are realistically at risk, but for those, leadership should treat this as a priority network-exposure and patching issue rather than a theoretical one.

Business Impact: High
Compensating Controls

Apply vendor patch (Apache Doris 4.0.8 or 4.1.4). Where immediate upgrade is not possible, keep FE metadata service endpoints off attacker-reachable networks and enforce firewall/security-group allowlists restricted to trusted cluster and administrative hosts; monitor FE access logs for anomalous source addresses.

Threat Intelligence Overview

EPSS Score
0.6%
Top 50% exploitable
Prevalence
Medium
popular open-source MPP analytical database, common but not everywhere
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy