Live › vulnerability › CVE-2026-121631
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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 17:21 UTC. All times on this page are UTC.
Self-hosted or managed Lightdash deployments in the affected range that have multiple projects and users with update permission on at least one project. Exposure depends on users being authenticated, so single-project or single-tenant setups carry less risk. Deployments already on 3.137.0 or later are not affected.
No product ranges from the sources yet.
0.2609.0 to 3.137.03.137.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-121631")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.