Skip to content
VulniPulse
Advisory severityHigh7.5Apache Software Foundation

High [CVE-2026-31377] Improper Authentication vulnerability in the Apache Doris Frontend (FE) meta service allows an unauthenticated remote attacker to access internal metadata service endpoints

This high-severity Apache Software Foundation advisory covers CVE-2026-31377 affecting Apache Doris Frontend.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-31377 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected versions
  • 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
  • 4.1.0 before 4.1.4
  • through 2.0
  • through 2.1
  • through 3.0
  • through 3.1

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Fixed versions
  • 4.0.8
  • 4.1.4

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to a fixed release (4.0.8 or 4.1.4), which fixes the issue.

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.