dbcve.org
GrafanaApplication

CVE-2021-41244

HIGH · 7.2 CVSS v3.1 Published 2021-11-15
Fix available
A fix is available. Upgrade to 8.2.4 or later.
See remediation →
78/100
Remediation priority · High
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
Grafana is an open-source platform for monitoring and observability. In affected versions when the fine-grained access control beta feature is enabled and there is more than one organization in the Grafana instance admins are able to access users from other organizations. Grafana 8.0 introduced a mechanism which allowed users with the Organization Admin role to list, add, remove, and update users’ roles in other organizations in which they are not an admin. With fine-grained access control enabled, organization admins can list, add, remove and update users' roles in another organization, where they do not have organization admin role. All installations between v8.0 and v8.2.3 that have fine-grained access control beta enabled and more than one organization should be upgraded as soon as possible. If you cannot upgrade, you should turn off the fine-grained access control using a feature flag.

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

When Grafana's fine-grained access control beta feature is enabled with multiple organizations, Organization Admins can list, add, remove, and update users' roles in other organizations where they do not have admin privileges. This is an authorization bypass that allows cross-organization user manipulation.

MitigationUpgrade to Grafana v8.2.4 or later; alternatively, disable the fine-grained access control beta feature via the feature flag if upgrading is not immediately possible.

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
GrafanaApplication
Affected:>= 8.0.0, < 8.2.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Check Grafana version
    Run `grafana-server --version` or check the version file in the Grafana installation directory, or query the Grafana HTTP API endpoint `/api/health`
    Affected if The installed version is 8.0.0 or higher but lower than 8.2.4
  2. Verify fine-grained access control is enabled
    Inspect the Grafana configuration file (grafana.ini) for the `[feature_toggles]` section, or check environment variables for `GF_FEATURE_TOGGLES_ENABLE` containing `fgac` or `fineGrainedAccessControl`
    Affected if The fine-grained access control beta feature flag is enabled
  3. Confirm multiple organizations exist
    Query the Grafana HTTP API `/api/orgs` with an Organization Admin token, or inspect the database table `org` to count organizations
    Affected if More than one organization is configured in the Grafana instance

The environment is affected if Grafana version is between 8.0.0 and 8.2.3 inclusive, the fine-grained access control beta feature is enabled, and multiple organizations are configured.

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 8.2.4 or later
Fixed in 8.2.4
Interim mitigation

Upgrade to Grafana v8.2.4 or later; alternatively, disable the fine-grained access control beta feature via the feature flag if upgrading is not immediately possible.

Recommended fix High confidence

Grafana 8.2.4 or later (latest 8.x stable)

  1. Check current Grafana version using `grafana-cli --version` or the UI/admin page
  2. Backup Grafana configuration and database before upgrading
  3. Upgrade Grafana to version 8.2.4 or later (recommended: latest 8.x stable release)
  4. If immediate upgrade is not possible, disable fine-grained access control by setting `GF_FEATURE_TOGGLES_ENABLE = none` or removing `enable` from `GF_FEATURE_TOGGLES` in grafana.ini
  5. Verify the upgrade was successful and fine-grained access control is functioning correctly

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

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-41244 — 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-2021-41244 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