dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-36500

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue in the cluster-admin:backup-datastore component of Controller v12.0.5 allows attackers to execute a directory traversal via a crafted request.

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 directory traversal vulnerability in the backup-datastore component of Controller v12.0.5 allows attackers to craft malicious requests that access files outside the intended backup directory. The cluster-admin component designation indicates this runs with elevated privileges, and CVSS 9.1 suggests network-exploitable with no authentication required, potentially allowing complete system compromise.

MitigationUpgrade to a patched version of Controller. If no patch exists, implement strict input validation on file path parameters in backup-datastore requests, restrict filesystem permissions, and apply web application firewall rules to block traversal sequences (.., /, \).

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Controller installation and version
    Locate the Controller installation directory and check for version markers (version file, manifest, or about page). Common paths: /opt/controller, /usr/local/controller, or check the service banner via 'curl -s http://localhost:<port>/api/version' if the API is exposed.
    Affected if The installed version is 12.0.5 specifically, as this is the only version listed as affected.
  2. Verify backup-datastore component is present
    Check for the cluster-admin:backup-datastore component in the Controller installation. Look for directories or binaries named 'backup-datastore', 'backup', or 'datastore' within the Controller file structure. Check component listings if available via CLI: 'controller-cli component list' or similar.
    Affected if The backup-datastore component exists in the installation.
  3. Confirm backup functionality is enabled
    Check Controller configuration files (typically in conf/ or config/ directories) for backup-related settings. Look for 'backup.enabled', 'backup.datastore', or similar configuration keys. Query the API if accessible: GET /api/v1/backup/status
    Affected if Backup functionality is explicitly enabled in the configuration.
  4. Inspect backup storage path configuration
    Examine backup datastore configuration files for the 'storage.path', 'backup.location', or 'datastore.path' setting. This defines the intended backup storage directory. Look in conf/backup.properties, config/backup.yaml, or similar.
    Affected if A backup storage path is configured (the vulnerability allows traversing outside this path).
  5. Check for unauthorized file access indicators
    Review server logs for suspicious access patterns: look for directory traversal attempts in backup-related endpoints. Search logs for patterns like '../', '..\', or unusual file paths in backup operations. Check /var/log/ or Controller's log directory for backup-datastore access logs.
    Affected if Log entries show backup operations accessing paths outside the configured storage directory, or traversal sequences in request parameters.

The environment is affected if Controller version 12.0.5 is installed with the backup-datastore component enabled and configured for backups.

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

Upgrade to a patched version of Controller. If no patch exists, implement strict input validation on file path parameters in backup-datastore requests, restrict filesystem permissions, and apply web application firewall rules to block traversal sequences (.., /, \).

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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