{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32252 exists.","fix":"No fix has been published for CVE-2026-32252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32252 is a high-severity missing authorization vulnerability in chartbrew, published on 10 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-32252 and fix it if it is affected.\n\nWhat it is: CVE-2026-32252 is a high-severity missing authorization vulnerability in chartbrew, published on 10 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-32252 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-32252/ (Markdown: https://insights.sbomify.com/CVE-2026-32252/index.md)","id":"CVE-2026-32252","markdown":"https://insights.sbomify.com/CVE-2026-32252/index.md","name":"CVE-2026-32252","record":{"aliases":["GHSA-mw4f-cf22-qpcj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Chartbrew web application","requires_auth":"low_privilege","summary":"An authenticated attacker can bypass tenant isolation to read project data from other teams due to missing authorization checks in the template generation endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"chartbrew","vendor":"depomo"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 4.9.0, a cross-tenant authorization bypass exists in Chartbrew in GET /team/:team_id/template/generate/:project_id. The GET handler calls checkAccess(req, \"updateAny\", \"chart\") without awaiting the returned promise, and it does not verify that the supplied project_id belongs to req.params.team_id or to the caller's team. As a result, an authenticated attacker with valid template-generation permissions in their own team can request the template model for a project belonging to another team and receive victim project data. This vulnerability is fixed in 4.9.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 Cross-Tenant Template Export and Secret Disclosure in `GET /team/:team_id/template/generate/:project_id`","id":"CVE-2026-32252","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":"Sunshine: Authentication bypass via improper client certificate validation","id":"CVE-2026-32253"},"packages":[],"prev":{"headline":"Tolgee has an XXE Injection in Translation Import","id":"CVE-2026-32251"},"products":["chartbrew"],"published":"2026-04-10","related":[{"cvss_score":8.8,"headline":"Chartbrew: Remote Code Execution (RCE) via Vulnerable API","id":"CVE-2026-25888","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.8,"headline":"Chartbrew: SQL injection in date-type variable handling (applyMysqlOrPostgresVariables)","id":"CVE-2026-27005","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.7,"headline":"Missing authorization in chartbrew","id":"CVE-2026-27603","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":7.8,"headline":"Chartbrew has SSRF in API Data Connection - No IP Validation on User-Provided URLs","id":"CVE-2026-30232","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":7.2,"headline":"Chartbrew: Remote Code Execution (RCE) via MongoDB Dataset Query","id":"CVE-2026-25887","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":6.5,"headline":"Chartbrew: Insecure Direct Object Reference (IDOR) in Chart Operations","id":"CVE-2026-25877","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["chartbrew"]},"summary":"An authenticated attacker can bypass tenant isolation to read project data from other teams due to missing authorization checks in the template generation endpoint.","url":"https://insights.sbomify.com/CVE-2026-32252/"}