vciy

CVE-2023-38646

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 open source before 0.46.6.1 and Metabase Enterprise before 1.46.6.1 allow attackers to execute arbitrary commands on the server, at the…

CVE-2023-386463 of 4 sources documented this
62

rank 62 = 30 + 25 + 0 + 7 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.98677  ·  without this subject the record ranks 32

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 37

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 62

How much of the world it touches

NVD CPE configurations

8 products in the CPE ranges  ·  without this subject the record ranks 55

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.92Mover the next 30 days, if this record is yours
Movement-$89,100on 2024-09-03, the last material move, 1 year, 10 months before this reading
Basisassumeda published average, not your estate

$4.92M = $4.99M incident cost x 1 exposure x 0.98677 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.98677EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-17, 492 days at 0.99, as of 2026-07-22. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

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 · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchmetabase 0.43.7.2; metabase 0.44.7.1; metabase 0.45.4.1; metabase 0.46.6.1; metabase 1.43.7.2; metabase 1.44.7.1receipt
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: Proof-of-concept published · 39 public repositories, 2023-07-28.

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

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.98677 · top 0.08% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes49 · last 16 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesMetabasereceipt
Published rangesmetabase < 0.43.7.2; metabase < 1.43.7.2; metabase >= 0.44.0 < 0.44.7.1; metabase >= 0.45.0 < 0.45.4.1receipt
Show all 8 published ranges
metabase < 0.43.7.2
metabase < 1.43.7.2
metabase >= 0.44.0 < 0.44.7.1
metabase >= 0.45.0 < 0.45.4.1
metabase >= 0.46.0 < 0.46.6.1
metabase >= 1.44.0 < 1.44.7.1
metabase >= 1.45.0 < 1.45.4.1
metabase >= 1.46.0 < 1.46.6.1

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 open source before 0.46.6.1 and Metabase Enterprise before 1.46.6.1 allow attackers to execute arbitrary commands on the server, at the server's privilege level. Authentication is not required for exploitation. The other fixed versions are 0.45.4.1, 1.45.4.1, 0.44.7.1, 1.44.7.1, 0.43.7.2, and 1.43.7.2. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
affected versions
metabase < 0.43.7.2; metabase < 1.43.7.2; metabase >= 0.44.0 < 0.44.7.1; and 5 more, listed in full below

check it yourself metabase.com github.com news.ycombinator.com github.com packetstormsecurity.com packetstormsecurity.com receipt

Dated events

2023-08-01EPSS moved 0.00 to 0.082023-08-09EPSS moved 0.08 to 0.512025-03-17EPSS moved 0.80 to 0.94

Movement the material steps

22 Jul 20230.00048
9 Aug 20230.50882 · crossed 0.10 and 0.50
28 Oct 20230.60885
7 Feb 20240.89125
16 Feb 20240.90394 · crossed 0.90
20 Jun 20240.89858 · crossed 0.90
2 Jul 20240.90624 · crossed 0.90
3 Sep 20240.88910 · crossed 0.90
21 Nov 20240.76645
17 Dec 20240.66485
18 Dec 20240.79262
17 Mar 20250.93978 · crossed 0.90 · scoring model v2025.03.14
15 Jun 20260.97924 · scoring model v2026.06.15
22 Jul 20260.98677

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 45 observations
22 Jul 20230.00048
29 Jul 20230.00066
1 Aug 20230.07704
9 Aug 20230.50882
10 Aug 20230.54087
23 Oct 20230.58459
28 Oct 20230.60885
5 Nov 20230.60445
24 Dec 20230.62661
26 Jan 20240.70109
3 Feb 20240.66372
7 Feb 20240.89125
14 Feb 20240.87902
16 Feb 20240.90394
27 Feb 20240.90444
8 Mar 20240.91664
1 Apr 20240.92872
23 Apr 20240.91302
27 May 20240.90839
9 Jun 20240.90098
20 Jun 20240.89858
2 Jul 20240.90624
16 Jul 20240.91055
27 Jul 20240.90661
22 Aug 20240.90695
3 Sep 20240.88910
29 Sep 20240.86549
12 Oct 20240.84454
25 Oct 20240.80001
21 Nov 20240.76645
17 Dec 20240.66485
18 Dec 20240.79262
31 Dec 20240.76971
28 Jan 20250.81253
10 Feb 20250.79733
25 Feb 20250.80070
11 Mar 20250.80352
17 Mar 20250.93978
15 Apr 20250.94219
31 May 20250.94261
27 Jun 20250.94255
18 Nov 20250.93978
21 Nov 20250.94255
15 Jun 20260.97924
22 Jul 20260.98677

45 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.98677Published2023-07-21Public PoC2023-07-28Index as of2026-07-22

Exploit probability more than doubled between 2023-07-29 and 2023-08-01 (0.00066 → 0.07704) and the record had been public for 3 years when this index was last written.

Published 2023-07-21 receipt · Public PoC 2023-07-28 receipt · Index as of 2026-07-22 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-38646.

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.