# CVE-2026-121631: Lightdash authorization bypass in RenameService

Source: https://junglewise.ai/threats/cve-2026-121631-lightdash-0-2609-0-before-3-137-0-contains-an-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-121631 · Severity: medium · CVSS 4.2 · Published 2026-11-03

Lightdash is a business intelligence and analytics tool that helps teams explore and visualize data from warehouses. An authenticated user with permissions on one project can bypass authorization checks to read metadata from or corrupt dashboards in unrelated projects they should not access. An attacker could modify dashboard filters to break charts for other users or extract field names from restricted projects.

Technologies: [Lightdash](https://junglewise.ai/threats/technologies/lightdash). Vendors: [Lightdash](https://junglewise.ai/threats/vendors/lightdash).

## Quick answers

**Is CVE-2026-121631 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-121631 being exploited in the wild.

**How severe is CVE-2026-121631?** Medium severity, with a CVSS score of 4.2, published 3 November 2026.

**Which products and versions are affected?** Lightdash 0.2609.0 to before 3.137.0.

**Is there a fix for CVE-2026-121631?** Yes: fixed in 3.137.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-121631 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-121631?** Check whether you run Lightdash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.137.0

## Technical details

The RenameService fails to validate that a dashboard's projectUuid matches the projectUuid in the request URL before performing permission checks and data operations. An authenticated attacker with update permissions on Project A can send POST requests to rename endpoints with Project B's dashboard UUID, causing the permission check to pass (against Project A) while the data modification targets Project B. The GET endpoint similarly allows reading field metadata by UUID alone without project membership validation.

## Affected products

- Lightdash Lightdash 0.2609.0 to before 3.137.0

## Timeline

- 2026-11-03: disclosed
- 2026-11-03: patched

## References

- [https://github.com/lightdash/lightdash/releases/tag/3.137.0](https://github.com/lightdash/lightdash/releases/tag/3.137.0)
- [https://github.com/lightdash/lightdash/security/advisories/GHSA-h6fw-x63x-9gr6](https://github.com/lightdash/lightdash/security/advisories/GHSA-h6fw-x63x-9gr6)

## Related threats

- [Lightdash dbt Cloud webhook unauthenticated access and path traversal](https://junglewise.ai/threats/cve-2026-61654-lightdash-is-an-open-source-business-intelligence-platform-in)
- [Lightdash dbt Cloud webhook SSRF and unauthenticated access](https://junglewise.ai/threats/cve-2026-61576-lightdash-is-an-open-source-business-intelligence-platform-in)
- [Lightdash authorization bypass in personal access token deletion](https://junglewise.ai/threats/cve-2026-108747-lightdash-through-2-556-0-contains-an-authorization-bypass)
- [Lightdash SSRF in webhook delivery](https://junglewise.ai/threats/cve-2026-72846-lightdash-ssrf-in-webhook-delivery)