dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7715

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability has been found in ravenwits mcp-server-arangodb up to 0.4.7. This affects the function arango_backup of the file src/tools.ts of the component MCP Interface. Such manipulation of the argument outputDir leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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 · moderate confidence

A path traversal vulnerability exists in the arango_backup function within src/tools.ts of the MCP Interface component of mcp-server-arangodb. The outputDir argument is not properly validated, allowing attackers to manipulate file paths to access directories outside the intended scope.

MitigationImplement strict input validation and path sanitization for the outputDir parameter to ensure it resolves to an allowed directory. Use path.resolve() and validate the final path is within expected boundaries before file operations.

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

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
Low
Integrity
Low
Availability
Low

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

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 if mcp-server-arangodb is installed
    Run 'npm list mcp-server-arangodb' or check your node_modules directory for the package, or look for the mcp-server-arangodb binary in your PATH
    Affected if The package is present in your environment
  2. Determine the installed version
    Run 'npm list mcp-server-arangodb --depth=0' to see the installed version, or check package.json if you have the source
    Affected if The installed version lacks the path validation fix for the arango_backup outputDir parameter
  3. Locate the arango_backup function source
    Find the src/tools.ts file in the mcp-server-arangodb installation and locate the arango_backup function definition
    Affected if The function exists and accepts an outputDir parameter without validation
  4. Inspect outputDir validation in the function
    Examine the arango_backup function code for path sanitization - look for path.resolve(), path.isAbsolute(), or directory boundary checks before using outputDir in file operations
    Affected if The outputDir argument is used directly in file operations without validation or sanitization checks
  5. Verify MCP exposure of the backup function
    Check your MCP server configuration or tool definitions to confirm the arango_backup function is exposed as an available tool
    Affected if The vulnerable arango_backup function is exposed via the MCP interface and reachable by clients

You are affected if mcp-server-arangodb is installed with the arango_backup function exposed and the outputDir parameter in src/tools.ts lacks path traversal validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path sanitization for the outputDir parameter to ensure it resolves to an allowed directory. Use path.resolve() and validate the final path is within expected boundaries before file operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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