# CVE-2026-46484: Headplane: Path Traversal + RBAC Bypass in renameNode allows authenticated OIDC users to expire or rename any node/user

> Authenticated users can exploit path traversal and RBAC bypass to rename or expire any node or user in the Headscale network.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-vgj6-hcf2-fqf6

## What is CVE-2026-46484?

CVE-2026-46484 is a high-severity path traversal vulnerability in tale headplane, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-46484?


## How do I fix CVE-2026-46484?

No fix has been published for CVE-2026-46484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46484 being exploited?

There is no known exploitation of CVE-2026-46484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46484 and fix it if it is affected.

What it is: CVE-2026-46484 is a high-severity path traversal vulnerability in tale headplane, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46484 in the wild and no public exploit code.

Affected product: tale headplane. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46484/ (Markdown: https://insights.sbomify.com/CVE-2026-46484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46484
- OSV: https://osv.dev/vulnerability/CVE-2026-46484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46484/
Summaries are generated and may contain mistakes; the official description above is the record.