{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40904 exists.","fix":"No fix has been published for CVE-2026-40904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40904 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."},"fix_prompt":"Check this codebase for CVE-2026-40904 and fix it if it is affected.\n\nWhat it is: CVE-2026-40904 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40904 exists.\n\nAffected product: chartbrew. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40904/ (Markdown: https://insights.sbomify.com/CVE-2026-40904/index.md)","id":"CVE-2026-40904","markdown":"https://insights.sbomify.com/CVE-2026-40904/index.md","name":"CVE-2026-40904","record":{"aliases":["GHSA-jq95-gqww-vhm3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Chartbrew web application","requires_auth":"low_privilege","summary":"Authenticated attackers can access and modify datasets and data requests across projects within the same team due to insufficient permission checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"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 multiple dataset and dataRequest endpoints that authorize low-privileged project members at the team level instead of binding the requested dataset_id, dataRequest id, and connection_id to the caller's allowed projects. An authenticated attacker who only has access to one project inside a team can read, execute, create, update, and delete datasets and data requests that belong to other projects in the same team. The issue is exploitable remotely with ordinary project-level credentials and leads to cross-project data disclosure and unauthorized use of victim-side database or API connections. This issue has been patched in version 5.0.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Chartbrew: Incorrect Access Control in dataset and dataRequest routes via team-scoped permission checks","id":"CVE-2026-40904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"LinkAce: Password Reset Poisoning via X-Forwarded-Host Header Injection Leading to Account Takeover","id":"CVE-2026-40905"},"packages":[],"prev":{"headline":"Goshs - ArtiPACKED Vulnerability – GitHub Actions Credential Persistence","id":"CVE-2026-40903"},"products":["chartbrew"],"published":"2026-04-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-30","vendors":["chartbrew"]},"summary":"Authenticated attackers can access and modify datasets and data requests across projects within the same team due to insufficient permission checks.","url":"https://insights.sbomify.com/CVE-2026-40904/"}