dbcve.org
DorisApplication · Apache

CVE-2026-58319

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain Apache Doris FE HTTP REST administrative APIs were accessible without proper authentication. An unauthenticated attacker with network access to the FE HTTP service could perform unauthorized administrative operations, potentially affecting cluster integrity and availability and leading to cluster instability or denial of service. This issue affects Apache Doris versions prior to 3.1.0. Users are advised to upgrade to Apache Doris 3.1.0 or later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Doris Frontend (FE) HTTP REST administrative APIs lack authentication checks, allowing unauthenticated remote attackers to execute administrative operations by sending HTTP requests to the FE service port. This enables full cluster compromise including data manipulation, configuration changes, and denial of service.

MitigationUpgrade Apache Doris to version 3.1.0 or later. If immediate upgrade is not feasible, restrict network access to FE HTTP ports via firewall or network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DorisApplication
Affected:< 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Doris Frontend version
    Check the FE process version: grep -r 'version' in the FE metadata directory, or look for version file in the FE home directory (often under fe/meta or similar). Common command: cat fe/version 2>/dev/null || find . -name 'version' -type f 2>/dev/null | xargs cat
    Affected if Version is below 3.1.0 (e.g., 3.0.x, 2.x.x, 1.x.x)
  2. Verify FE HTTP REST API port is accessible
    Check if the FE HTTP port (default 8030) is listening and exposed: netstat -tlnp | grep 8030 or ss -tlnp | grep 8030. Verify network accessibility from untrusted networks if possible.
    Affected if Port 8030 (or configured FE HTTP port) is listening and accessible from network segments beyond localhost
  3. Test FE administrative API accessibility
    Send an unauthenticated HTTP request to a known administrative endpoint. Common FE API paths: /api/fe/config, /api/fe/health, /api/query/profile. Example: curl -s http://<fe-host>:8030/api/fe/config
    Affected if The request returns valid JSON response with cluster configuration or status without requiring authentication (HTTP 200 instead of 401/403)
  4. Check FE authentication configuration
    Inspect fe.conf for authentication settings: grep -i 'http' fe.conf | grep -i 'auth' or look for 'enable_authentication' or similar flags. Also check if http authentication is explicitly configured.
    Affected if No HTTP authentication is configured, or the configuration explicitly disables auth for REST APIs (enable_authentication=false or missing)
  5. Review FE HTTP filter/security settings
    Check fe.conf or associated security configuration files for http authentication filter settings. Look for: http_authenticate, http_filter, or security filter configurations.
    Affected if No HTTP authentication filter is defined for the REST API endpoints, or authentication is disabled for the FE HTTP server

You are affected if Apache Doris FE version is below 3.1.0 AND the FE HTTP REST API port is network-accessible AND the administrative APIs respond without authentication challenges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Upgrade Apache Doris to version 3.1.0 or later. If immediate upgrade is not feasible, restrict network access to FE HTTP ports via firewall or network segmentation.

Recommended fix High confidence

Apache Doris 3.1.0 or later

  1. Review the Apache Doris 3.1.0 release notes and migration guide for any specific upgrade requirements
  2. Perform a full backup of the Doris cluster metadata and data
  3. Schedule a maintenance window and ensure cluster is in a stable state
  4. Stop all FE (Frontend) nodes gracefully
  5. Upgrade FE nodes to version 3.1.0 or later
  6. Restart FE nodes and verify they are healthy (check logs and FE status)
  7. Stop all BE (Backend) nodes gracefully
  8. Upgrade BE nodes to version 3.1.0 or later
Caveat Review 3.1.0 release notes for potential breaking changes; major version upgrades may introduce compatibility considerations with existing queries and configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Doris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58319 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data