dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-46484

HIGH · 8.1 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.

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

Headplane versions prior to 0.6.3 and 0.7.0-beta.3 contain a path traversal and authorization bypass vulnerability in the Headscale API client, specifically affecting node and user rename operations. This flaw allows attackers to potentially access resources or perform actions outside the intended authorization boundaries by manipulating file paths or API requests.

MitigationUpgrade Headplane to version 0.6.3 or 0.7.0-beta.3 to patch the vulnerability. Review access controls around node and user rename operations as a precautionary measure.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Headplane installation and version
    Check the running Headplane service version using the package manager, Docker image tag, or the application itself if it exposes a version endpoint. Common methods: 'docker ps' for container version, or check the binary/service version with 'headplane --version' if CLI available.
    Affected if Headplane version is found to be lower than 0.6.3 or between 0.7.0-beta.1 and 0.7.0-beta.2 (if using beta versions).
  2. Verify Headscale API client is in use
    Examine the Headplane configuration files for references to Headscale integration. Look for settings related to the Headscale API client, node management, or user management modules. Check if the rename operations for nodes or users are configured or enabled.
    Affected if Headplane is configured to use the Headscale API client for node or user rename operations, and the version is vulnerable.
  3. Check network exposure of Headplane service
    Review network configuration or firewall rules to determine if the Headplane instance is exposed to untrusted networks. Inspect service binding addresses (e.g., listen on 0.0.0.0 vs 127.0.0.1) and any reverse proxy configurations.
    Affected if Headplane is network-accessible beyond trusted networks, which increases exploitability for unauthenticated attack vectors mentioned in the CVE.

You are affected if Headplane is running with a version prior to 0.6.3 or 0.7.0-beta.3 and uses the Headscale API client for node or user rename functionality.

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 Headplane to version 0.6.3 or 0.7.0-beta.3 to patch the vulnerability. Review access controls around node and user rename operations as a precautionary measure.

Recommended fix High confidence

Upgrade to Headplane version 0.6.3 (stable) or 0.7.0-beta.3 (beta)

  1. 1. Identify the current Headplane version currently running in your environment
  2. 2. If running a version prior to 0.6.3 (stable) or 0.7.0-beta.3 (beta), plan for upgrade
  3. 3. Consult the Headplane release notes or GitHub repository for upgrade instructions specific to your deployment method (e.g., Docker, binary, source)
  4. 4. Backup any existing Headplane configuration and data
  5. 5. Upgrade to version 0.6.3 (stable) or 0.7.0-beta.3 (beta) following your deployment method's standard upgrade procedure
  6. 6. Verify the upgrade was successful and Headplane is functioning correctly
  7. 7. Test node and user rename operations to confirm the path traversal vulnerability is remediated
Caveat No breaking changes mentioned in the advisory; upgrade is recommended due to security severity

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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