CVE-2026-17183: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-f74r-h7qj-c63f
CVSS 7.1
CWE-863
Published
Advisory Summary

CVE-2026-17183 is a HIGH (CVSS 7.1) security vulnerability vulnerability (CWE-863: Incorrect Authorization) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-17183 at a Glance

CVE Identifier CVE-2026-17183
GHSA Identifier GHSA-f74r-h7qj-c63f
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-863: Incorrect Authorization
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-17183

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-17183, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Summary An authenticated organization user who can create or edit alert rules in a folder can query a datasource for which they do not have datasources:query permission. The attacker sets the client-controlled query field queryType to __expr__ while retaining the UID of a real datasource. The alert-rule authorization path treats the query as a server-side expression and skips datasource permission enforcement, while the evaluator subsequently resolves and executes the query against the real datasource identified by datasourceUid. ## Impact This bypass can expose data accessible through Grafana's configured datasource credentials to a low-privileged user who is not authorized to query that datasource directly. Confidentiality impact is High. Integrity impact is Low because some datasource backends and configured credentials may permit state-changing queries. No availability impact has been demonstrated. ## Attack prerequisites - Authenticated, low-privileged user in the same Grafana organization - Permission to create or edit alert rules in an accessible folder - No datasources:query permission for the targeted datasource - Knowledge or discovery of the targeted datasource UID - No user interaction required ## Technical details / root cause 1. The attacker submits an alert-rule query with queryType: "__expr__" and the UID of a real datasource. 2. The datasource authorization helper skips permission enforcement when query.QueryType == "__expr__". 3. queryType is client-controlled and is not validated against the referenced datasource. 4. During evaluation, Grafana selects and loads the actual datasource using DatasourceUID, not the spoofed queryType. 5. The query therefore executes using Grafana's datasource credentials despite the caller lacking datasources:query. The root cause is inconsistent query classification between authorization and execution: authorization trusts queryType, while execution trusts DatasourceUID. ## Affected product / component - Product: Grafana OSS - Component: Unified Alerting / ngalert - Area: Alert-rule datasource authorization and query evaluation - Confirmed version: Grafana OSS 13.0.1 - Affected version range: not yet assessed ## Severity - CVSS 3.1: 7.1 High - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N - CWE-863: Incorrect Authorization Scope is Unchanged because the vulnerable authorization decision and resulting impact remain within Grafana's security authority. ## Source - Researcher: czarflix - Intigriti report: GRAFANALABS-F996ATD7 - Report URL: https://app.intigriti.com/company/submissions/GRAFANALABS-F996ATD7 ## Related report / duplicate assessment This is a default-Grafana-OSS reproduction of the root cause previously reported in GRAFANALABS-IAQAFIXI. The earlier submission was archived as Not Applicable because its proof of concept depended on Cloud/Enterprise-specific permission mechanisms, and the researcher was invited to demonstrate the issue under default OSS permissions. This report establishes that missing prerequisite and should be treated as the actionable OSS submission, not dismissed as a duplicate. VUL-2026-0095 and VUL-2026-0126 concern Enterprise Recorded Queries and have different components, endpoints, and root causes; they are related authorization issues but not duplicates. ## Recommended remediation - Do not exempt a query from datasource authorization based solely on client-controlled queryType. - Resolve the referenced datasource server-side before authorization and apply datasources:query whenever the resolved UID represents a real datasource. - Require expression queries to reference only the canonical server-side expression datasource and reject mismatches such as queryType: "__expr__" paired with a real datasource UID. - Ensure authorization and evaluation use the same canonical datasource identity and fail closed when fields conflict. - Add regression coverage for an OSS user with folder-level alert-rule edit permission but without datasource query permission, including mismatched queryType and datasourceUid values.

References

Frequently Asked Questions

What is CVE-2026-17183?
CVE-2026-17183 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-863: Incorrect Authorization.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-17183?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-17183?
CVE-2026-17183 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2026-17183?
CVE-2026-17183 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Maven dependencies for CVE-2026-17183?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f74r-h7qj-c63f",
  "modified" : "2026-08-19T18:32:52Z",
  "published" : "2026-08-19T18:32:52Z",
  "aliases" : [ "CVE-2026-17183" ],
  "details" : "Summary\n\nAn authenticated organization user who can create or edit alert rules in a folder can query a datasource for which they do not have datasources:query permission. The attacker sets the client-controlled query field queryType to __expr__ while retaining the UID of a real datasource.\n\nThe alert-rule authorization path treats the query as a server-side expression and skips datasource permission enforcement, while the evaluator subsequently resolves and executes the query against the real datasource identified by datasourceUid.\n\n## Impact\n\nThis bypass can expose data accessible through Grafana's configured datasource credentials to a low-privileged user who is not authorized to query that datasource directly. Confidentiality impact is High.\n\nIntegrity impact is Low because some datasource backends and configured credentials may permit state-changing queries. No availability impact has been demonstrated.\n\n## Attack prerequisites\n\n- Authenticated, low-privileged user in the same Grafana organization\n- Permission to create or edit alert rules in an accessible folder\n- No datasources:query permission for the targeted datasource\n- Knowledge or discovery of the targeted datasource UID\n- No user interaction required\n\n## Technical details / root cause\n\n1. The attacker submits an alert-rule query with queryType: \"__expr__\" and the UID of a real datasource.\n2. The datasource authorization helper skips permission enforcement when query.QueryType == \"__expr__\".\n3. queryType is client-controlled and is not validated against the referenced datasource.\n4. During evaluation, Grafana selects and loads the actual datasource using DatasourceUID, not the spoofed queryType.\n5. The query therefore executes using Grafana's datasource credentials despite the caller lacking datasources:query.\n\nThe root cause is inconsistent query classification between authorization and execution: authorization trusts queryType, while execution trusts DatasourceUID.\n\n## Affected product / component\n\n- Product: Grafana OSS\n- Component: Unified Alerting / ngalert\n- Area: Alert-rule datasource authorization and query evaluation\n- Confirmed version: Grafana OSS 13.0.1\n- Affected version range: not yet assessed\n\n## Severity\n\n- CVSS 3.1: 7.1 High\n- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N\n- CWE-863: Incorrect Authorization\n\nScope is Unchanged because the vulnerable authorization decision and resulting impact remain within Grafana's security authority.\n\n## Source\n\n- Researcher: czarflix\n- Intigriti report: GRAFANALABS-F996ATD7\n- Report URL: https://app.intigriti.com/company/submissions/GRAFANALABS-F996ATD7\n\n## Related report / duplicate assessment\n\nThis is a default-Grafana-OSS reproduction of the root cause previously reported in GRAFANALABS-IAQAFIXI. The earlier submission was archived as Not Applicable because its proof of concept depended on Cloud/Enterprise-specific permission mechanisms, and the researcher was invited to demonstrate the issue under default OSS permissions. This report establishes that missing prerequisite and should be treated as the actionable OSS submission, not dismissed as a duplicate.\n\nVUL-2026-0095 and VUL-2026-0126 concern Enterprise Recorded Queries and have different components, endpoints, and root causes; they are related authorization issues but not duplicates.\n\n## Recommended remediation\n\n- Do not exempt a query from datasource authorization based solely on client-controlled queryType.\n- Resolve the referenced datasource server-side before authorization and apply datasources:query whenever the resolved UID represents a real datasource.\n- Require expression queries to reference only the canonical server-side expression datasource and reject mismatches such as queryType: \"__expr__\" paired with a real datasource UID.\n- Ensure authorization and evaluation use the same canonical datasource identity and fail closed when fields conflict.\n- Add regression coverage for an OSS user with folder-level alert-rule edit permission but without datasource query permission, including mismatched queryType and datasourceUid values.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-17183"
  }, {
    "type" : "WEB",
    "url" : "https://grafana.com/security/security-advisories/cve-2026-17183"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-19T18:16:35Z"
  }
}