---
id: "CVE-2026-121631"
kind: "vulnerability"
aliases: ["CVE-2026-121631"]
title: "Lightdash: authorization bypass lets users alter dashboards in other projects"
severity: "medium"
cvss: 4.2
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "lightdash", "multi-project", "self-hosted"]
not_affected_if: ["no-update-permission-users", "single-project", "version-3.137.0-or-later"]
published_at: "2026-11-03T17:18:11+00:00"
first_seen_at: "2026-11-03T17:21:56+00:00"
updated_at: "2026-11-03T17:24:42+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121631", "first_seen_at": "2026-11-03T17:21:56+00:00"}]
---

# Lightdash: authorization bypass lets users alter dashboards in other projects

Lightdash versions from 0.2609.0 before 3.137.0 fail to check that a dashboard belongs to the project named in the request during rename operations. An authenticated user with update permission on one project can read field metadata from, and modify dashboard filters in, a different project.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Lightdash version and compare it against the affected range `0.2609.0` to `3.137.0`
- Review whether untrusted or many users hold project update permission across multiple projects

## Fix

- Upgrade Lightdash to `3.137.0` or later

## Timeline

- 2026-11-03T17:21:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-121631

## Documents

- [advisory] Vendor advisory: github.com https://github.com/lightdash/lightdash/security/advisories/GHSA-h6fw-x63x-9gr6
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/lightdash-before-cross-project-idor-via-renameservice-dashboard-endpoints
- [fix] Release notes: github.com https://github.com/lightdash/lightdash/releases/tag/3.137.0

## From the sources

Lightdash 0.2609.0 before 3.137.0 contains an authorization bypass vulnerability in the RenameService that allows authenticated users with update Project permission on one project to access and modify dashboards belonging to a different project, caused by the failure to verify that the projectUuid from the URL matches the projectUuid of the target dashboard. Attackers can send crafted POST requests to the rename/dashboard endpoint to modify foreign dashboard filters and break charts, or send GET requests to the rename/dashboard/fields endpoint to read field metadata from projects they do not have access to.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_