# CVE-2026-40603: Chartbrew: Incorrect Access Control in /api/project/dashboard/:brewName via same-team override

> Low-privileged users can access unauthorized project dashboards and recover stored report passwords due to missing project-level authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 30 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-6qr3-g75h-xm3f

## What is CVE-2026-40603?

CVE-2026-40603 is a medium-severity missing authorization vulnerability in chartbrew, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In version 4.9.0, Chartbrew exposes a legacy dashboard route that returns a project's report data to any authenticated member of the same team, even when that user does not have access to the specific project. The route bypasses project-level authorization and returns the raw project object. As a result, a low-privileged same-team user can read another project's dashboard data and recover the project's stored report password from the response. This issue has been patched in version 5.0.0.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-40603 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40603 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40603 is a medium-severity missing authorization vulnerability in chartbrew, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40603 exists.

Affected product: chartbrew. 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-40603/ (Markdown: https://insights.sbomify.com/CVE-2026-40603/index.md)
```

## Sources

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

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