How severe is CVE-2023-38646?

No CVSS score has been assigned to CVE-2023-38646 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2023-38646?

Affected package information for CVE-2023-38646 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-38646?

Upgrade the affected component to the fixed release for CVE-2023-38646, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect CVE-2023-38646 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2023-38646 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-38646 actively exploited in the wild?

Yes. There are 25 known exploit references for CVE-2023-38646, including 15 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-38646?

CVE-2023-38646 has an EPSS (Exploit Prediction Scoring System) score of 98.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2023-38646?

A Nuclei detection template exists for CVE-2023-38646, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-38646 published, and has it been updated?

CVE-2023-38646 was published on July 21, 2023 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2023-38646 — metabase

CVE-2023-38646 is a security vulnerability. 25 public exploit references exist, so weaponization risk is real. A fix is available — see the affected versions and patch details below.

Published

Jul 21, 2023

Updated

Oct 21, 2026

Affected

1 product

Patched

See advisory

Exploits

25 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

98.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

1 product · 8 configurations

Application

metabasemetabase

≥ 1.46.0 && < 1.46.6.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.