CVE-2025-27141
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 · uneditedMetabase Enterprise Edition is the enterprise version of Metabase business intelligence and data analytics software. Starting in version 1.47.0 and prior to versions 1.50.36, 1.51.14, 1.52.11, and 1.53.2 of Metabase Enterprise Edition, users with impersonation permissions may be able to see results of cached questions, even if their permissions don’t allow them to see the data. If some user runs a question which gets cached, and then an impersonated user runs that question, then the impersonated user sees the same results as the previous user. These cached results may include data the impersonated user should not have access to. This vulnerability only impacts the Enterprise Edition of Metabase and not the Open Source Edition. Versions 1.53.2, 1.52.11, 1.51.14, and 1.50.36 contains a patch. Versions on the 1.49.X, 1.48.X, and 1.47.X branches are vulnerable but do not have a patch available, so users should upgrade to a major version with an available fix. Disabling question caching is a workaround for this issue.
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 confidenceIn Metabase Enterprise Edition, users with impersonation permissions can view cached results from previously run questions, potentially exposing sensitive data they shouldn't have access to. When a user runs a question that gets cached, subsequent impersonated users accessing that same cached question will see the original user's results instead of being restricted by their own permissions.
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>= 1.47.0, < 1.50.36>= 1.51.0, < 1.51.14>= 1.52.0, < 1.52.11>= 1.53.0, < 1.53.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Metabase editionIn the Metabase admin panel, go to Settings > About or check the UI footer for 'Enterprise Edition' label. Alternatively, check the license info.Affected if Running Enterprise Edition (not open source)
-
Verify installed versionGo to Settings > About in the admin panel to see the exact version number, or check the startup logs.Affected if Version falls in ranges: >=1.47.0 and <1.50.36, OR >=1.51.0 and <1.51.14, OR >=1.52.0 and <1.52.11, OR >=1.53.0 and <1.53.2
-
Confirm question caching is enabledIn admin settings, go to Settings > Caching (or Performance settings in some versions) and check if caching is turned on, or query the setting via API: GET /api/setting/enable-query-cachingAffected if Question caching is enabled globally or for specific databases
-
Check for active impersonation permissionsIn admin settings, go to Permissions > Data permissions or Users > Impersonation. Look for any users or groups configured with impersonation roles.Affected if Any user or group has impersonation permissions configured
You are affected if running Enterprise Edition in a vulnerable version range with question caching enabled and impersonation permissions in use, allowing cached query results to leak between users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.50.361.51.141.52.11
Upgrade to version 1.50.36, 1.51.14, 1.52.11, or 1.53.2 (or later) which contain the patch. Alternatively, disable question caching as a workaround if immediate upgrading is not feasible.
Upgrade to version 1.50.36, 1.51.14, 1.52.11, or 1.53.2 (choose the version that matches your current major branch)
- 1. Verify if you are using Metabase Enterprise Edition (this vulnerability only affects Enterprise Edition, not Open Source Edition)
- 2. Check your current Metabase version in the admin settings
- 3. Plan upgrade to a fixed version based on your current branch: if on 1.47.x-1.49.x upgrade to 1.50.36 or later; if on 1.50.x upgrade to 1.50.36; if on 1.51.x upgrade to 1.51.14; if on 1.52.x upgrade to 1.52.11; if on 1.53.x upgrade to 1.53.2
- 4. Review upgrade documentation at www.metabase.com for your specific version path
- 5. Test the upgrade in a non-production environment before deploying to production
- 6. After upgrading, verify that user impersonation permissions work correctly with cached questions
- 7. Alternatively, as a workaround if immediate upgrade is not possible: disable question caching in admin settings under "Performance" to mitigate the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-27141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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