# CVE-2026-40600: Chartbrew: Incorrect Access Control in project share policy routes via unbound policy_id

> Authenticated users can modify or delete sharing policies of other projects due to missing ownership validation on policy IDs.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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-pq8h-2h99-39xm

## What is CVE-2026-40600?

CVE-2026-40600 is a high-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 allows authenticated users with access to one project to update or delete a SharePolicy record that belongs to a different project. The affected routes authorize the caller against the project in the URL path, but they never verify that policy_id belongs to that project. This permits cross-project modification of dashboard sharing rules, including visibility, password requirements, allowed parameters, and expiration settings. This issue has been patched in version 5.0.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-40600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40600 is a high-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-40600 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-40600/ (Markdown: https://insights.sbomify.com/CVE-2026-40600/index.md)
```

## Sources

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

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