CVE-2025-58337: Apache Doris-MCP-Server · Improper Access Control
Affects Apache Doris-MCP-ServerSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium · fixed in 0.6.0 : update Apache Doris-MCP-Server when convenient.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.doris/doris-mcp-serverpkg:maven/org.apache.doris/doris-mcp-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade Apache Doris-MCP-Server to version 0.6.0 immediately, as this release contains the official fix for CVE-2025-58337. 2. Audit and restrict the issuance of read-only accounts, ensuring they are granted only to trusted users and systems. 3. Implement strict monitoring and alerting on any modification attempts from read-only accounts to detect potential exploitation early. 4. Employ network segmentation and access controls to limit exposure of the Doris-MCP-Server to only necessary users and systems. 5. Use multi-factor authentication (MFA) for all accounts, including read-only users, to reduce the risk of credential compromise. 6. Regularly review and update access control policies and permissions to enforce the principle of least privilege rigorously. 7. Conduct periodic security assessments and penetration testing focusing on access control mechanisms within Apache Doris deployments. 8. Maintain comprehensive logging and audit trails for all user activities to facilitate forensic investigations if unauthorized modifications are suspected.
Description
An attacker with a valid read-only account can bypass Doris MCP Server’s read-only mode due to improper access control, allowing modifications that should have been prevented by read-only restrictions. Impact: Bypasses read-only mode; attackers with read-only access may perform unauthorized modifications. Recommended action for operators: Upgrade to version 0.6.0 as soon as possible (this release contains the fix).