- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 14
- Public CVEs
- 103
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays from $1,500
- for critical bugs.
- Report on Sorona
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Sorona lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical | $1,500+ | |
| High | $700+ | |
| Medium | $300+ | |
| Low |
|
$100 $100 / 1 month Claude Max |
- Safe harbor
-
Partial
Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.
- Hall of fame
-
Yes
Recognition is a Hall of Fame listing and a CVE where applicable
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
14 assets you may test, 6 excluded.
Web 1
- https://grafana.com/oss/grafana
Products and areas 13
- Alerting in full, including rule evaluation, contact points, notification templates and the outbound requests each contact point makes
- Annotations, the explore surface and the transformation pipeline that runs over query results
- Authentication in full: the built-in login, OAuth and generic OIDC providers, SAML, LDAP, auth proxy headers, service accounts and API keys
- Dashboard JSON, panel options and the rendering of every panel type, the point at which attacker-influenced strings meet the browser
- Grafana Labs' policy asks for reports through its Intigriti vulnerability disclosure programme or [email protected] and states that no bounty is offered for any report. It declares no boundary narrower than the Grafana product itself
- Provisioning and the file-based configuration path, plus anything that reads configuration from disk or the environment
- Query construction for the SQL data sources, where a template variable or panel option becomes part of the statement the backend runs
- Snapshots, public dashboards, embedded panels and anonymous access, all of which expose a surface without a logged-in user
- The data source proxy and every data source plugin shipped in core, covering the URL the backend is asked to fetch and the credentials attached to it
- The HTTP API in full, including the admin endpoints and everything the UI does not surface
- The image renderer integration and any other path where Grafana renders content out of process
- The permission model across organisations, teams, folders, dashboards and data sources, including the role-based access control layer
- The plugin system: loading, signature verification, the backend plugin process boundary and the plugin catalogue install path
Out of scope (6)
- A deployment an operator deliberately configured with anonymous access, a permissive auth proxy or public dashboards enabled
- Findings against an unsupported Grafana release, since fixes land on the supported minor versions
- Grafana Cloud infrastructure, which is a hosted service and a separate asset from the open-source product
- Loki, Mimir, Tempo and Pyroscope, sibling products in their own repositories with their own advisory streams
- The data source backends themselves: a defect in Prometheus or Postgres belongs to that project
- Third-party and community plugins not published by Grafana Labs
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.
While testing
-
Submit through sorona.xyz.
-
Re-verify the programme state before you start.
-
Name the Grafana version and the authentication configuration.
-
Say which data source type the finding runs through.
-
Distinguish open-source Grafana from Grafana Enterprise features.
-
Hold detail until the advisory is out.
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-14199 | Only self-managed Grafana instances with Auth Proxy authentication and identity caching enabled (sync_ttl greater than zero) are affected. The Auth Proxy cache key concatenated the username and forwarded identity attributes without a delimiter, so distinct identities could collide on one key. An authenticated user who shapes their own attributes to collide with a higher-privileged user's, while th | High 7.1 | 2 Sep 2026 |
| CVE-2026-8609 | An unauthenticated attacker can repeatedly call Grafana's OAuth login route with unique values, causing unbounded memory growth that can eventually exhaust memory and crash the Grafana instance (denial of service). | Medium 5.3 | 10 Jul 2026 |
| CVE-2026-8595 | A user with Editor permissions can craft a dashboard whose table (TableNG) panel contains a malicious field name that executes as a script in the browser of any user who views the dashboard (stored cross-site scripting). | Medium 6.8 | 10 Jul 2026 |
| CVE-2026-33382 | Several Grafana API endpoints, some of them unauthenticated, do not limit the size of the request body before processing it. An attacker can send very large payloads that force excessive memory allocation, potentially exhausting memory and causing a denial of service. | High 7.5 | 10 Jul 2026 |
| CVE-2026-28378 | The public dashboard deletion endpoint does not enforce organization isolation, allowing an Org Admin in one organization to delete public dashboards belonging to a different organization by supplying the target dashboard's identifiers. | Low 3.1 | 7 Jul 2026 |
| CVE-2026-42127 | The public dashboard query endpoint does not limit request body size before processing, allowing unauthenticated attackers to trigger excessive memory allocation by sending arbitrarily large JSON payloads. This can lead to denial of service through memory exhaustion. No valid dashboard access token or authentication is required to exploit this vulnerability. | High 7.5 | 22 Jun 2026 |
| CVE-2026-9029 | A user with Editor permissions can place a malicious script in the attribution field of a Geomap panel's XYZ tile layer via a template variable. The script then executes in the browser of any user who views the affected dashboard (stored cross-site scripting). | High 7.3 | 22 Jun 2026 |
| CVE-2026-42129 | A user with Viewer permissions can use a path traversal in the Loki data source plugin to reach administrative Loki endpoints and read sensitive backend configuration and internal service information. | High 7.7 | 22 Jun 2026 |
| CVE-2026-28381 | The Snowflake datasource allows for GET/PUT commands, which can allow any user with access to run queries against the data source to read/write files between the local grafana server and the connected Snowflake host. | Critical 9.6 | 22 Jun 2026 |
| CVE-2026-10601 | A user with Viewer permissions can use specially crafted requests to the Tempo and Loki data source plugins to reach unintended backend endpoints. Depending on the backend configuration this can expose data source credentials, leak internal responses, or trigger administrative actions on the configured backend. | Medium 5.4 | 22 Jun 2026 |
| CVE-2026-27878 | A TraceQL query in Grafana Tempo with a large exemplars hint value can cause the Tempo instance to allocate an excessive amount of memory, resulting in an out-of-memory crash. This could allow an authenticated user to trigger a denial of service against the Tempo service. | Medium 6.5 | 19 Jun 2026 |
| CVE-2026-11769 | We have released version 5.24.0 of the Grafana Operator. This patch includes a MEDIUM severity security fix for a path traversal/privilege escalation vulnerability in the Grafana Operator. ### Summary The Grafana Operator supports loading dashboards & library panels using the jsonnet data templating language. The jsonnet expression is evaluated in the context of the operator manager pod. ### Impac | Medium 6.4 | 13 Jun 2026 |
| CVE-2026-33378 | Using the $__timeGroup macro, one can achieve an OOM by overloading the server. This requires a SQL datasource. If the server is set up to auto-restart, the impact is minimal or non-existent, as the attack can take upwards of half an hour to crash the server. | Medium 6.5 | 13 May 2026 |
| CVE-2026-33380 | A vulnerability in SQL Expressions allows an authenticated attacker to read arbitrary files from the Grafana server's filesystem. Only instances with the sqlExpressions feature toggle enabled are vulnerable. | Medium 6.3 | 13 May 2026 |
| CVE-2026-33381 | When a user's access to mint tokens for a service account is revoked, it is sometimes still possible to do so for a few seconds after the event. The user will eventually lose access to do this. | Medium 5.9 | 13 May 2026 |
| CVE-2026-28374 | Editors could delete any annotation, even those they do not have read access to. The editor user cannot create or read the annotations. | Medium 4.3 | 13 May 2026 |
| CVE-2026-28376 | The Grafana Live push endpoint can be exploited to cause unbounded memory allocation by sending a large or streaming request body, potentially leading to out-of-memory conditions. An authenticated user with access to the Grafana Live API can trigger this issue. | Medium 6.5 | 13 May 2026 |
| CVE-2026-28379 | A race condition in Grafana Live allows authenticated users with Viewer role to trigger a server crash by sending concurrent requests that cause a fatal map access error. This results in complete service unavailability requiring restart of the Grafana server. | Medium 6.5 | 13 May 2026 |
| CVE-2026-28380 | Any Editor could delete any snapshot, even if they have no access to read or write them. | Medium 6.5 | 13 May 2026 |
| CVE-2026-28383 | A request to the Grafana plugin resources endpoint can cause unbounded memory allocation by reading the entire request body into memory. An authenticated user can exploit this to trigger an out-of-memory condition, potentially causing a denial of service. | Medium 6.5 | 13 May 2026 |
| CVE-2026-33376 | When using an IPv6 allow-list for the Auth Proxy feature, it defaults to /32 addresses. Addresses specifying a mask explicitly are not affected; to mitigate easily, add the desired mask (usually /128) to the addresses. Only auth proxy is affected; Okta, SAML, LDAP, etc are unaffected here. | High 7.4 | 13 May 2026 |
| CVE-2026-33377 | An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege. | High 7.1 | 13 May 2026 |
| CVE-2026-21728 | Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service. | High 7.5 | 24 Apr 2026 |
| CVE-2026-21726 | The CVE-2021-36156 fix validates the namespace parameter for path traversal sequences after a single URL decode, by double encoding, an attacker can read files at the Ruler API endpoint /loki/api/v1/rules/{namespace} Thanks to Prasanth Sundararajan for reporting this vulnerability. | Medium 5.3 | 15 Apr 2026 |
| CVE-2026-21727 | A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records. Due to a backward compatibility condition allowing org_id = 0 records to be returned across organizations, a user with datasource management privileges could read and permanently delete legacy correlation data belonging to another organization. This issue affects correlations cr | Low 3.3 | 15 Apr 2026 |
| CVE-2025-41118 | Pyroscope is an open-source continuous profiling database. The database supports various storage backends, including Tencent Cloud Object Storage (COS). If the database is configured to use Tencent COS as the storage backend, an attacker could extract the secret_key configuration value from the Pyroscope API. To exploit this vulnerability, an attacker needs direct access to the Pyroscope API. We h | Critical 9.1 | 15 Apr 2026 |
| CVE-2025-12141 | In Grafana's alerting system, users with edit permissions for a contact point, specifically the permissions “alert.notifications:write” or “alert.notifications.receivers:test” that are granted as part of the fixed role "Contact Point Writer", which is part of the basic role Editor - can edit contact points created by other users, modify the endpoint URL to a controlled server. By invoking the test | Low 1.3 | 15 Apr 2026 |
| CVE-2026-28375 | A testdata data-source can be used to trigger out-of-memory crashes in Grafana. | Medium 6.5 | 27 Mar 2026 |
| CVE-2026-27879 | A resample query can be used to trigger out-of-memory crashes in Grafana. | Medium 6.5 | 27 Mar 2026 |
| CVE-2026-27880 | The OpenFeature feature toggle evaluation endpoint reads unbounded values into memory, which can cause out-of-memory crashes. | High 7.5 | 27 Mar 2026 |
| CVE-2026-27876 | A chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE). This is enabled by a feature in Grafana (OSS), so all users are always recommended to update to avoid future attack vectors going this path. Only instances with the sqlExpressions feature toggle enabled are vulnerable. Only instances in the following version ranges are a | Critical 9.1 | 27 Mar 2026 |
| CVE-2026-27877 | When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-sources as far as possible to improve your deployments' security. | Medium 6.5 | 27 Mar 2026 |
| CVE-2026-28377 | A vulnerability in Grafana Tempo exposes the S3 SSE-C encryption key in plaintext through the /status/config endpoint, potentially allowing unauthorized users to obtain the key used to encrypt trace data stored in S3. Thanks to william_goodfellow for reporting this vulnerability. | High 7.5 | 26 Mar 2026 |
| CVE-2026-33375 | The Grafana MSSQL data source plugin contains a logic flaw that allows a low-privileged user (Viewer) to bypass API restrictions and trigger a catastrophic Out-Of-Memory (OOM) memory exhaustion, crashing the host container. | Medium 6.5 | 26 Mar 2026 |
| CVE-2026-21724 | A vulnerability has been discovered in Grafana OSS where an authorization bypass in the provisioning contact points API allows users with Editor role to modify protected webhook URLs without the required alert.notifications.receivers.protected:write permission. | Medium 5.4 | 26 Mar 2026 |
| CVE-2026-21725 | A time-of-create-to-time-of-use (TOCTOU) vulnerability lets recently deleted-then-recreated data sources be re-deleted without permission to do so. This requires several very stringent conditions to be met: - The attacker must have admin access to the specific datasource prior to its first deletion. - Upon deletion, all steps within the attack must happen within the next 30 seconds and on the same | Low 2.6 | 25 Feb 2026 |
| CVE-2026-21722 | Public dashboards with annotations enabled did not limit their annotation timerange to the locked timerange of the public dashboard. This means one could read the entire history of annotations visible on the specific dashboard, even those outside the locked timerange. This did not leak any annotations that would not otherwise be visible on the public dashboard. | Medium 5.3 | 12 Feb 2026 |
| CVE-2025-41117 | Stack traces in Grafana's Explore Traces view can be rendered as raw HTML, and thus inject malicious JavaScript in the browser. This would require malicious JavaScript to be entered into the stack trace field. Only datasources with the Jaeger HTTP API appear to be affected; Jaeger gRPC and Tempo do not appear affected whatsoever. | Medium 6.8 | 12 Feb 2026 |
| CVE-2026-21721 | The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is an organization‑internal privilege escalation. | High 8.1 | 27 Jan 2026 |
| CVE-2026-21720 | Every uncached /avatar/:hash request spawns a goroutine that refreshes the Gravatar image. If the refresh sits in the 10-slot worker queue longer than three seconds, the handler times out and stops listening for the result, so that goroutine blocks forever trying to send on an unbuffered channel. Sustained traffic with random hashes keeps tripping this timeout, so goroutine count grows linearly, e | High 7.5 | 27 Jan 2026 |
| CVE-2025-41115 | SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management. In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric exte | Critical 10.0 | 21 Nov 2025 |
| CVE-2025-4123 | A cross-site scripting (XSS) vulnerability exists in Grafana caused by combining a client path traversal and open redirect. This allows attackers to redirect users to a website that hosts a frontend plugin that will execute arbitrary JavaScript. This vulnerability does not require editor permissions and if anonymous access is enabled, the XSS will work. If the Grafana Image Renderer plugin is inst | High 7.6 | 22 May 2025 |
| CVE-2024-10452 | Organization admins can delete pending invites created in an organization they are not part of. | Low 2.2 | 29 Oct 2024 |
| CVE-2024-9264 | The SQL Expressions experimental feature of Grafana allows for the evaluation of `duckdb` queries containing user input. These queries are insufficiently sanitized before being passed to `duckdb`, leading to a command injection and local file inclusion vulnerability. Any user with the VIEWER or higher permission is capable of executing this attack. The `duckdb` binary must be present in Grafana's | Critical 9.4 | 18 Oct 2024 |
| CVE-2024-8996 | Unquoted Search Path or Element vulnerability in Grafana Agent (Flow mode) on Windows allows Privilege Escalation from Local User to SYSTEM This issue affects Agent Flow: before 0.43.2 | High 7.3 | 25 Sep 2024 |
| CVE-2024-8975 | Unquoted Search Path or Element vulnerability in Grafana Alloy on Windows allows Privilege Escalation from Local User to SYSTEM This issue affects Alloy: before 1.3.3, from 1.4.0-rc.0 through 1.4.0-rc.1. | High 7.3 | 25 Sep 2024 |
| CVE-2024-5526 | Grafana OnCall is an easy-to-use on-call management tool that will help reduce toil in on-call management through simpler workflows and interfaces that are tailored specifically for engineers. Grafana OnCall, from version 1.1.37 before 1.5.2 are vulnerable to a Server Side Request Forgery (SSRF) vulnerability in the webhook functionallity. This issue was fixed in version 1.5.2 | High 7.7 | 5 Jun 2024 |
| CVE-2024-1442 | A user with the permissions to create a data source can use Grafana API to create a data source with UID set to *. Doing this will grant the user access to read, query, edit and delete all data sources within the organization. | Medium 6.0 | 7 Mar 2024 |
| CVE-2023-5123 | The JSON datasource plugin ( https://grafana.com/grafana/plugins/marcusolsson-json-datasource/ ) is a Grafana Labs maintained plugin for Grafana that allows for retrieving and processing JSON data from a remote endpoint (including a specific sub-path) configured by an administrator. Due to inadequate sanitization of the dashboard-supplied path parameter, it was possible to include path traversal c | High 8.0 | 14 Feb 2024 |
| CVE-2023-5122 | Grafana is an open-source platform for monitoring and observability. The CSV datasource plugin is a Grafana Labs maintained plugin for Grafana that allows for retrieving and processing CSV data from a remote endpoint configured by an administrator. If this plugin was configured to send requests to a bare host with no path (e.g. https://www.example.com/ https://www.example.com/` ), requests to an e | Medium 5.0 | 14 Feb 2024 |
| CVE-2023-6152 | A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up. | Medium 5.4 | 13 Feb 2024 |
| CVE-2023-3010 | Grafana is an open-source platform for monitoring and observability. The WorldMap panel plugin, versions before 1.0.4 contains a DOM XSS vulnerability. | High 7.3 | 25 Oct 2023 |
| CVE-2023-4399 | Grafana is an open-source platform for monitoring and observability. In Grafana Enterprise, Request security is a deny list that allows admins to configure Grafana in a way so that the instance doesn’t call specific hosts. However, the restriction can be bypassed used punycode encoding of the characters in the request address. | Medium 6.6 | 17 Oct 2023 |
| CVE-2023-4457 | Grafana is an open-source platform for monitoring and observability. The Google Sheets data source plugin for Grafana, versions 0.9.0 to 1.2.2 are vulnerable to an information disclosure vulnerability. The plugin did not properly sanitize error messages, making it potentially expose the Google Sheet API-key that is configured for the data source. This vulnerability was fixed in version 1.2.2. | Medium 5.5 | 16 Oct 2023 |
| CVE-2023-4822 | Grafana is an open-source platform for monitoring and observability. The vulnerability impacts Grafana instances with several organizations, and allows a user with Organization Admin permissions in one organization to change the permissions associated with Organization Viewer, Organization Editor and Organization Admin roles in all organizations. It also allows an Organization Admin to assign or r | Medium 6.7 | 16 Oct 2023 |
| CVE-2023-3128 | Grafana is validating Azure AD accounts based on the email claim. On Azure AD, the profile email field is not unique and can be easily modified. This leads to account takeover and authentication bypass when Azure AD OAuth is configured with a multi-tenant app. | Critical 9.4 | 22 Jun 2023 |
| CVE-2023-2183 | Grafana is an open-source platform for monitoring and observability. The option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function. This might enable malicious users to abuse the functionality by sending multiple alert | Medium 4.1 | 6 Jun 2023 |
| CVE-2023-2801 | Grafana is an open-source platform for monitoring and observability. Using public dashboards users can query multiple distinct data sources using mixed queries. However such query has a possibility of crashing a Grafana instance. The only feature that uses mixed queries at the moment is public dashboards, but it's also possible to cause this by calling the query API directly. This might enable mal | High 7.5 | 6 Jun 2023 |
| CVE-2023-1387 | Grafana is an open-source platform for monitoring and observability. Starting with the 9.1 branch, Grafana introduced the ability to search for a JWT in the URL query parameter auth_token and use it as the authentication token. By enabling the "url_login" configuration option (disabled by default), a JWT might be sent to data sources. If an attacker has access to the data source, the leaked token | Medium 4.2 | 26 Apr 2023 |
| CVE-2023-1410 | Grafana is an open-source platform for monitoring and observability. Grafana had a stored XSS vulnerability in the Graphite FunctionDescription tooltip. The stored XSS vulnerability was possible due the value of the Function Description was not properly sanitized. An attacker needs to have control over the Graphite data source in order to manipulate a function description and a Grafana admin needs | Medium 6.2 | 23 Mar 2023 |
Original policy
Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 32 Last 12 months 103 Lifetime Access control 35 % Auth bypass 25 % SSRF 20 % Cross-site scripting 20 % Latest advisories Loading the feed Overview Grafana is the visualisation layer nearly every observability stack terminates in, bundled into Kubernetes platforms, appliances and vendor products far beyond its own direct installs. It authenticates operators and stores credentials for every data source it queries, from Prometheus and Postgres through to cloud provider APIs. A defect in its data source proxy or its permission model turns a dashboard viewer into a reader of the backends behind it. Grafana Labs ran a paid Intigriti programme tiered to $15,000 and shut it down; the current policy states it does not offer bounties for any vulnerability report. sorona.xyz pays you directly on qualified, reproduced findings. In scope Grafana Labs' policy asks for reports through its Intigriti vulnerability disclosure programme or [email protected] and states that no bounty is offered for any report. It declares no boundary narrower than the Grafana product itself Authentication in full: the built-in login, OAuth and generic OIDC providers, SAML, LDAP, auth proxy headers, service accounts and API keys The permission model across organisations, teams, folders, dashboards and data sources, including the role-based access control layer The data source proxy and every data source plugin shipped in core, covering the URL the backend is asked to fetch and the credentials attached to it Query construction for the SQL data sources, where a template variable or panel option becomes part of the statement the backend runs The plugin system: loading, signature verification, the backend plugin process boundary and the plugin catalogue install path Alerting in full, including rule evaluation, contact points, notification templates and the outbound requests each contact point makes Provisioning and the file-based configuration path, plus anything that reads configuration from disk or the environment Dashboard JSON, panel options and the rendering of every panel type, the point at which attacker-influenced strings meet the browser Snapshots, public dashboards, embedded panels and anonymous access, all of which expose a surface without a logged-in user The HTTP API in full, including the admin endpoints and everything the UI does not surface The image renderer integration and any other path where Grafana renders content out of process Annotations, the explore surface and the transformation pipeline that runs over query results Out of scope Grafana Cloud infrastructure, which is a hosted service and a separate asset from the open-source product Loki, Mimir, Tempo and Pyroscope, sibling products in their own repositories with their own advisory streams Third-party and community plugins not published by Grafana Labs The data source backends themselves: a defect in Prometheus or Postgres belongs to that project A deployment an operator deliberately configured with anonymous access, a permissive auth proxy or public dashboards enabled Findings against an unsupported Grafana release, since fixes land on the supported minor versions Most-valued findings Authorization defects that cross an organisation, team or folder boundary, since a single Grafana routinely serves several teams that are not meant to see each other's dashboards or data sources Server-side request forgery out of the data source proxy, alerting contact points or the image renderer. Grafana sits inside the network with credentials, so an outbound request it can be steered into reaches cloud metadata and internal services Authentication bypass and identity binding in the OAuth, OIDC, SAML and auth proxy paths, above all anything that attaches an attacker-controlled external identity to an existing account Data source credential disclosure through the API, provisioning or the proxy, since those credentials are standing access to the backends Stored cross-site scripting through dashboard JSON, panel options or annotation content, escalating to API calls in an administrator's session Plugin signature verification bypass, which turns the plugin catalogue into a code delivery path SQL injection in the query builders for the relational data sources, where a template variable escapes the parameterisation it was meant to take Anything reachable without authentication through snapshots, public dashboards or embedded panels, which are the surfaces most often left exposed to the internet Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report through the Grafana Labs vulnerability disclosure programme on Intigriti, or by email to [email protected] . GitHub private security advisories are also enabled on grafana/grafana The policy states directly that no bounty is offered for any vulnerability report. Recognition is a Hall of Fame listing and a CVE where applicable Re-verify the programme state before you start. The paid Intigriti bug bounty that covered this project was shut down recently rather than long ago, and it could return Name the Grafana version and the authentication configuration. Anonymous access, embedded panels and public dashboards each change what an unauthenticated caller can reach Say which data source type the finding runs through. The proxy behaves differently for SQL sources, Prometheus-style sources and cloud provider integrations Distinguish open-source Grafana from Grafana Enterprise features. Findings that only exist in a licensed feature sit outside the open-source tree Disclosure Coordinated with Grafana Labs through the Intigriti disclosure programme or the security address, published as an advisory with researcher credit alongside a patched release. Grafana ships security fixes in batched point releases across supported minor versions, so the practical embargo runs to that release rather than to a fixed day count. Hold detail until the advisory is out. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability