GHSA-MF33-GV72-W2H5

Vulnerability from github – Published: 2026-05-18 17:50 – Updated: 2026-05-18 17:50
VLAI
Summary
CloakBrowser: Unauthenticated path traversal via fingerprint parameter in cloakserve leads to arbitrary directory deletion
Details

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.

Impact

An attacker with network access to the cloakserve port can delete arbitrary directories accessible to the service user.

Patches

Fixed in v0.3.28.

Mitigations

  • Upgrade to v0.3.28 or later
  • Restrict network access to the cloakserve port
Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.3.27"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "cloakbrowser"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.28"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-45727"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-18T17:50:21Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "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.\n\nAdditionally, `cloakserve` bound to `0.0.0.0` by default, making it network-exposed.\n\n### Impact\n\nAn attacker with network access to the cloakserve port can delete arbitrary directories accessible to the service user.\n\n### Patches\n\nFixed in v0.3.28.\n\n### Mitigations\n\n- Upgrade to v0.3.28 or later\n- Restrict network access to the cloakserve port",
  "id": "GHSA-mf33-gv72-w2h5",
  "modified": "2026-05-18T17:50:21Z",
  "published": "2026-05-18T17:50:21Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/CloakHQ/CloakBrowser/security/advisories/GHSA-mf33-gv72-w2h5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/CloakHQ/CloakBrowser"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "CloakBrowser: Unauthenticated path traversal via fingerprint parameter in cloakserve leads to arbitrary directory deletion"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…