dbcve.org
Grafana OperatorApplication · Grafana

CVE-2026-11769

HIGH · 8.8 CVSS v3.1 Published 2026-06-13
Fix available
A fix is available. Upgrade to 5.24.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. ### Impact It is possible for a malicious user who can create Dashboard or LibraryPanel resources for a Grafana instance to obtain the Kubernetes service account token of the Grafana Operator manager. ### Affected versions All Grafana Operator versions <= 5.23 ### Solutions and mitigations All installations should be upgraded as soon as possible. As a workaround, the following ValidatingAdmissionPolicy prevent the creation or modification of jsonnet based resources: apiVersion: admissionregistration.k8s.io/v1 kind: ValidatingAdmissionPolicy metadata: name: "prevent-jsonnet-dashboards" spec: failurePolicy: Fail matchConstraints: resourceRules: - apiGroups: ["grafana.integreatly.org"] apiVersions: ["v1beta1"] operations: ["CREATE", "UPDATE"] resources: ["grafanadashboards", "grafanalibrarypanels"] validations: - expression: "!has(object.spec.jsonnetLib)" --- apiVersion: admissionregistration.k8s.io/v1 kind: ValidatingAdmissionPolicyBinding metadata: name: "prevent-jsonnet-dashboards-clusterwide" spec: policyName: "prevent-jsonnet-dashboards" validationActions: [Deny] ### Acknowledgement We would like to thank Artem Cherezov for responsibly disclosing the vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Grafana Operator evaluates jsonnet expressions in GrafanaDashboard and GrafanaLibraryPanel resources within the context of the operator manager pod. A malicious user with permission to create or modify these resources can execute arbitrary jsonnet code to read the operator's Kubernetes service account token, achieving privilege escalation to the operator's permissions.

MitigationUpgrade to Grafana Operator 5.24.0 immediately. As a temporary workaround, deploy the provided ValidatingAdmissionPolicy to block jsonnet-based Dashboard and LibraryPanel resources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Grafana OperatorApplication
Affected:< 5.24.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana Operator version
    Run `kubectl get deployment grafana-operator -n <namespace> -o jsonpath='{.spec.template.spec.containers[0].image}'` or check the operator pod image. Extract the version tag from the image name.
    Affected if The installed version is less than 5.24.0 (for example, 5.23.0, 5.22.0, etc.)
  2. Check for GrafanaDashboard resources with jsonnetLib
    Run `kubectl get grafanaDashboards -A -o json` and inspect each resource's spec for 'jsonnetLib' fields or 'jsonnet' entries that could contain malicious expressions.
    Affected if Any GrafanaDashboard resource contains jsonnetLib fields in its specification
  3. Check for GrafanaLibraryPanel resources with jsonnetLib
    Run `kubectl get grafanaLibraryPanels -A -o json` and inspect each resource's spec for 'jsonnetLib' fields or 'jsonnet' entries.
    Affected if Any GrafanaLibraryPanel resource contains jsonnetLib fields in its specification
  4. Verify RBAC permissions for dashboard and librarypanel resources
    Run `kubectl auth can-i create grafanaDashboards --all-namespaces` and `kubectl auth can-i create grafanaLibraryPanels --all-namespaces` to check if untrusted users have permissions to create these resources.
    Affected if Users other than cluster administrators can create or update GrafanaDashboard or GrafanaLibraryPanel resources

You are affected if the Grafana Operator version is below 5.24.0 AND users with limited permissions can create or modify Dashboard or LibraryPanel resources containing jsonnetLib fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.24.0 or later
Fixed in 5.24.0
Interim mitigation

Upgrade to Grafana Operator 5.24.0 immediately. As a temporary workaround, deploy the provided ValidatingAdmissionPolicy to block jsonnet-based Dashboard and LibraryPanel resources.

Recommended fix High confidence

Upgrade to Grafana Operator version 5.24.0

  1. Plan and schedule an upgrade of the Grafana Operator to version 5.24.0
  2. Backup current operator configuration and any custom resources (GrafanaDashboards, GrafanaLibraryPanels) before upgrading
  3. Upgrade the Grafana Operator to version 5.24.0 using your deployment method (e.g., Operator Lifecycle Manager, Helm chart, or manual kubectl apply)
  4. Verify the upgrade was successful by checking the operator deployment and confirming version 5.24.0 is running
  5. Monitor the operator and Grafana resources for any issues following the upgrade
  6. Alternatively, if immediate upgrade is not possible, apply the ValidatingAdmissionPolicy and ValidatingAdmissionPolicyBinding YAML provided in the advisory as a temporary workaround to block jsonnet-based resources

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Operator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11769 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data