dbcve.org
Doris Mcp ServerApplication · Apache

CVE-2025-66336

HIGH · 8.1 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 0.6.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
Apache Doris MCP Server contains a SQL injection vulnerability in a metadata query path. A user-controlled database name is directly interpolated into a SQL query, and the query is executed without passing the caller's authorization context. This may allow an authenticated attacker, or an anonymous attacker if authentication is disabled, to bypass SQL security validation and access metadata outside the intended database scope. Affected users are recommended to upgrade to Doris version 0.6.1 or later, which fixes the issue.

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 MCP Server has a SQL injection vulnerability where user-controlled database names are directly interpolated into SQL queries without sanitization. The critical issue is that the caller's authorization context is not passed to the query execution, allowing bypass of SQL security validation and unauthorized metadata access outside the intended database scope.

MitigationUpgrade Apache Doris to version 0.6.1 or later to obtain the patch for this SQL injection vulnerability.

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
Doris Mcp ServerApplication
Affected:>= 0.1.0, < 0.6.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 MCP Server installation
    Locate the Apache Doris MCP Server installation directory or check if the service is running. Common locations include /opt/apache-doris-mcp-server, /usr/local/doris-mcp, or check running processes for doris-mcp related entries.
    Affected if Apache Doris MCP Server is installed and running with version < 0.6.1
  2. Determine installed version
    Check the version of Apache Doris MCP Server. Common methods: (1) Check the VERSION file in the installation directory, (2) Run 'doris-mcp-server --version' or similar version command if available, (3) Check the JAR/WAR file version in the installation directory, (4) Query the service's API endpoint for version information if exposed.
    Affected if Installed version is 0.1.0 or higher but below 0.6.1
  3. Verify metadata query feature is accessible
    Identify if the metadata query endpoint/path is accessible and functional. Check if the MCP server exposes any metadata-related endpoints, database introspection features, or schema query capabilities that accept database names as input parameters.
    Affected if The metadata query functionality is enabled and accessible to users or applications
  4. Inspect database name handling in configuration
    Review configuration files for any metadata query settings. Look for configurations controlling database metadata access, query execution paths, or authorization enforcement. Check for any allowlist or security policy settings related to metadata access.
    Affected if Configuration shows metadata queries can be triggered without proper authorization context validation or with direct database name concatenation enabled
  5. Review audit logs for suspicious metadata queries
    Check application and audit logs for metadata query patterns that might indicate exploitation. Look for queries accessing databases outside expected scope, unusual SQL patterns, or queries with database names that could indicate injection attempts.
    Affected if Logs show metadata queries accessing unexpected databases or containing anomalous database name patterns

You are affected if Apache Doris MCP Server version is 0.1.0 or higher but below 0.6.1 AND the metadata query functionality is accessible to users or applications.

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 0.6.1 or later
Fixed in 0.6.1
Interim mitigation

Upgrade Apache Doris to version 0.6.1 or later to obtain the patch for this SQL injection vulnerability.

Recommended fix High confidence

0.6.1

  1. 1. Identify the current version of Apache Doris MCP Server in use (check via --version or package manager)
  2. 2. Review upgrade documentation for Doris MCP Server to understand migration requirements
  3. 3. Plan and schedule a maintenance window for the upgrade
  4. 4. Create a backup of the current configuration and any persistent data
  5. 5. Download Apache Doris MCP Server version 0.6.1 or later from official Apache sources
  6. 6. Stop the currently running Doris MCP Server service
  7. 7. Install the upgraded version (0.6.1 or later) following standard installation procedures
  8. 8. Restore configuration from backup, adapting if needed for new version

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

Fix this in Doris Mcp Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66336 — 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-2025-66336 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