dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-45727

HIGH · 8.8 CVSS v4.0 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/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
CloakBrowser is a tool to bypass bot detection tests. Prior to version 0.3.28, the cloakserve CDP multiplexer uses the user-supplied fingerprint query parameter directly as a filesystem path component when creating Chrome profile directories. An unauthenticated attacker who can reach the cloakserve port can supply a crafted fingerprint value containing path traversal sequences to resolve user_data_dir outside the configured data_dir. When Chrome fails to start or the process is cleaned up, shutil.rmtree() deletes the traversed path, resulting in arbitrary directory deletion. Additionally, cloakserve bound to 0.0.0.0 by default, making it network-exposed. This issue has been patched in version 0.3.28.

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

CloakBrowser's cloakserve CDP multiplexer accepts a user-supplied fingerprint query parameter that is used directly as a filesystem path component when creating Chrome profile directories. An unauthenticated remote attacker can supply path traversal sequences (e.g., ../../) in the fingerprint parameter to escape the intended data_dir and cause shutil.rmtree() to delete arbitrary directories on the system when Chrome fails to start or is cleaned up.

MitigationUpgrade to version 0.3.28 or later which patches this vulnerability. If immediate patching is not possible, restrict network access to cloakserve and implement input validation to reject fingerprint values containing path 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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 cloakserve is running
    Check for processes named cloakserve, or look for listening ports commonly used by CDP multiplexers (typically 9222, 9333, or custom ports from config)
    Affected if cloakserve process is found running on the system
  2. Determine cloakserve version
    Run 'cloakserve --version' or check the installed package version via package manager (pip show cloakserve, apt list installed, etc.)
    Affected if version is below 0.3.28
  3. Locate the configuration file
    Look for config files typically named config.yaml, config.json, or settings.conf in /etc/cloakserve/, ~/.cloakserve/, or the application working directory
    Affected if configuration exists and specifies a data_dir
  4. Verify network exposure
    Check the configuration or running process for bind address. Look for 0.0.0.0 in bind settings or netstat/ss output showing the port bound to all interfaces
    Affected if cloakserve is listening on 0.0.0.0 or a public IP rather than 127.0.0.1/localhost

User is affected if cloakserve is running with a version below 0.3.28 and is network-accessible, allowing unauthenticated attackers to exploit the fingerprint parameter path traversal for arbitrary directory deletion.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.3.28 or later which patches this vulnerability. If immediate patching is not possible, restrict network access to cloakserve and implement input validation to reject fingerprint values containing path traversal sequences.

Recommended fix High confidence

version 0.3.28

  1. Identify the CloakBrowser/cloakserve installation on the system
  2. Check the currently installed version (likely via pip show cloakbrowser or similar package manager command)
  3. Upgrade to version 0.3.28 or later using the package manager (e.g., pip install cloakbrowser>=0.3.28)
  4. Verify the upgrade was successful by checking the installed version
  5. If cloakserve was previously bound to 0.0.0.0, consider restricting the binding to localhost (127.0.0.1) if remote access is not required

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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