{"answers":{"affected":"1 open source package ship an affected version, including grafana.","exploited":"There is no known exploitation of CVE-2026-9703 in the wild and no public exploit code.","fix":"Upgrade grafana to a fixed version for your release line: 12.3.9, 12.4.6 or 13.0.4.","what":"CVE-2026-9703 is a high-severity missing authorization vulnerability in Grafana Enterprise, published on 15 Oct 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-9703 and fix it if it is affected.\n\nWhat it is: CVE-2026-9703 is a high-severity missing authorization vulnerability in Grafana Enterprise, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9703 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- grafana (Bitnami): affected from 8.0.0; fixed in 12.3.9, 12.4.6, 13.0.4\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-9703/ (Markdown: https://insights.sbomify.com/CVE-2026-9703/index.md)","id":"CVE-2026-9703","markdown":"https://insights.sbomify.com/CVE-2026-9703/index.md","name":"CVE-2026-9703","record":{"aliases":["BIT-grafana-2026-9703","GHSA-c6mh-c9x8-gf7q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Grafana monitoring platform","requires_auth":"low_privilege","summary":"Authenticated Viewer users can create, modify, or delete Loki alerting rules via the data source proxy due to missing access controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GRAFANA","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Grafana's data source proxy did not apply role-based access control to write requests forwarded to Loki data sources. A user holding only the Viewer role on an affected Grafana instance could send POST, PUT and DELETE requests through the proxy to the Loki rules API (/loki/api/v1/rules), allowing them to create, modify and delete Loki alerting rules. Because those rules are stored by Loki rather than by Grafana, the change took effect for every user of that Loki data source, not only for the Viewer who made the request.\n\nExploitation requires an authenticated Viewer account on the Grafana instance and a configured Loki data source; no other privileges are needed. Both Grafana OSS and Grafana Enterprise are affected. The defect is in Grafana's data source proxy; Loki itself is not vulnerable and does not need to be patched.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Viewer role can create, modify and delete Loki alerting rules","id":"CVE-2026-9703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Keycloak: keycloak: privilege escalation due to oversized subject_token jwt","id":"CVE-2026-9704"},"packages":[{"ecosystem":"Bitnami","fixed":["12.3.9","12.4.6","13.0.4"],"introduced":["8.0.0","12.4.0","13.0.0"],"last_affected":[],"package":"grafana","purl":"pkg:bitnami/grafana","source":"BIT-grafana-2026-9703"}],"prev":{"headline":"InPost PL \u003c 1.9.1 - Unauthenticated WooCommerce Order Parcel-Locker Hijacking","id":"CVE-2026-9702"},"products":["Grafana Enterprise","Grafana OSS"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Grafana"]},"summary":"Authenticated Viewer users can create, modify, or delete Loki alerting rules via the data source proxy due to missing access controls.","url":"https://insights.sbomify.com/CVE-2026-9703/"}