vciy

CVE-2025-27141

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Metabase Enterprise Edition allows cached questions to leak data to impersonated users

CVE-2025-271414 of 4 sources documented this
21

rank 21 = 0 + 16 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00364  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from NVD  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 16

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Unaudited dollar value2 of 3 inputs carry a receipt
Exposureunder $1over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

under $1 = $4.99M incident cost x 0 exposure x 0.00364 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00364EPSSNOT IN KEVas of 2026-09-20
Severity4.8 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-02-27, 569 days at 0.00, as of 2026-09-19. arc-rules@v1

Foresight · where to check next

Fortinet FortiOS,VMware WorkspaceMcAfee,LLC McAfeeCVE-2019-1575227141

This record is one instance of CWE-732, incorrect permission assignment for critical resource. The index holds 1762 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
GitHub_M4.8 MEDIUMreceipt
NVD6.5 MEDIUMreceipt
Scoring standard
GitHub_MCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running metabase? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · active user interaction · low attack complexity · no attack requirementsreceipt
ImpactNo confidentiality, integrity or availability impactreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-732 Incorrect Permission Assignment for Critical Resourcereceipt
Published consequencesCWE-732: Confidentiality: Read Application Data, Read Files or Directories; Access Control: Gain Privileges or Assume Identity; Integrity, Other: Modify Application Data, Other[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchmetabase 1.50.36; metabase 1.51.14; metabase 1.52.11; metabase 1.53.2receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA4.8 MEDIUMreceipt
CVSS, NVD6.5 MEDIUMreceipt
Exploit probability0.00364 · top 70% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes27 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productmetabasereceipt
Published rangesmetabase >= 1.47.0 < 1.50.36; metabase >= 1.51.0 < 1.51.14; metabase >= 1.52.0 < 1.52.11; metabase >= 1.53.0 < 1.53.2receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Metabase 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. receipt

Read the rest of the CNA's description

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.

NVD's analysis a second authority

severity
6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-732
affected versions
metabase >= 1.47.0 < 1.50.36; metabase >= 1.51.0 < 1.51.14; metabase >= 1.52.0 < 1.52.11; and 1 more, listed in full below
also scored by
[email protected] 4.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

The CNA scored it 4.8 and NVD 6.5. Both are shown because both were published; we do not pick one.

check it yourself github.com metabase.com metabase.com receipt

Movement the material steps

27 Feb 20250.00045
17 Mar 20250.00027 · scoring model v2025.03.14
15 Jun 20260.00336 · scoring model v2026.06.15
19 Sep 20260.00364
Show all 27 observations
27 Feb 20250.00045
1 Mar 20250.00070
17 Mar 20250.00027
28 Mar 20250.00031
29 Mar 20250.00035
30 Mar 20250.00031
3 May 20250.00036
26 Jun 20250.00046
23 Jul 20250.00038
24 Jul 20250.00042
4 Aug 20250.00054
20 Sep 20250.0006
30 Sep 20250.00068
30 Oct 20250.00074
10 Nov 20250.00086
18 Nov 20250.00104
20 Nov 20250.00107
21 Nov 20250.00088
11 Dec 20250.00095
21 Dec 20250.00112
4 Apr 20260.00136
5 Apr 20260.00158
6 Apr 20260.00161
15 Jun 20260.00336
23 Jul 20260.00351
28 Aug 20260.00357
19 Sep 20260.00364

27 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00364Published2025-02-24Index as of2026-09-19

The record had been public for 1 year, 6 months when this index was last written.

Published 2025-02-24 receipt · Index as of 2026-09-19 derived

The pattern, elsewhere

This record is one instance of CWE-732, incorrect permission assignment for critical resource. The index holds 1762 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2018-13374 · Fortinet FortiOS, fortiADConly 1 attribute comparableKEV listed · 2019receipt
CVE-2022-22960 · VMware Workspace ONE Access, Identity…only 1 attribute comparableKEV listed · 2022receipt
CVE-2021-23874 · McAfee,LLC McAfee Total Protection (MTP)only 1 attribute comparableKEV listed · 2021receipt
CVE-2019-15752nothing comparable heldKEV listed · 2019receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

1762 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-27141.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.