VulnerabilityPublished 9 Jun 2025

CVE-2025-5895: Metabase · ReDoS

Affects MetabaseSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmetabase/metabase`pkg:github/metabase/metabase`Other threats	Affected =54.10	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should promptly apply the patch identified by commit 4454ebbdc7719016bf80ca0f34859ce5cee9f6b0 to upgrade Metabase beyond version 54.10. In addition to patching, organizations should implement input validation and rate limiting on endpoints that process data URIs to reduce the risk of resource exhaustion. Deploying Web Application Firewalls (WAFs) with rules to detect and block suspiciously complex regular expression patterns or malformed data URIs can provide an additional layer of defense. Monitoring system resource usage and setting alerts for unusual CPU spikes in Metabase servers can help detect exploitation attempts early. Organizations should also consider isolating Metabase instances in segmented network zones to limit the blast radius of potential attacks. Regularly reviewing and updating incident response plans to include scenarios involving denial of service via application-layer vulnerabilities is recommended.

Description

A vulnerability was found in Metabase 54.10. It has been classified as problematic. This affects the function parseDataUri of the file frontend/src/metabase/lib/dom.js. The manipulation leads to inefficient regular expression complexity. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The patch is named 4454ebbdc7719016bf80ca0f34859ce5cee9f6b0. It is recommended to apply a patch to fix this issue.

Impact

For European organizations using Metabase 54.10, this vulnerability poses a risk primarily to service availability. Metabase is a popular open-source business intelligence tool used for data visualization and analytics. Organizations relying on Metabase for critical reporting and decision-making could experience service disruptions if an attacker exploits this vulnerability to trigger resource exhaustion. This could lead to degraded performance or temporary denial of service, impacting business continuity and operational efficiency. While the vulnerability does not directly expose sensitive data or allow unauthorized data modification, the potential downtime or instability could indirectly affect compliance with data availability requirements under regulations such as GDPR. Additionally, organizations in sectors with high reliance on data analytics, such as finance, healthcare, and manufacturing, may face operational risks if Metabase services become unavailable.

Summary

CVE-2025-5895 is a medium-severity vulnerability identified in Metabase version 54.10, specifically within the frontend component located at frontend/src/metabase/lib/dom.js in the parseDataUri function. The issue arises from inefficient regular expression complexity, which can lead to excessive CPU consumption when processing specially crafted input. This type of vulnerability is commonly known as a Regular Expression Denial of Service (ReDoS). An attacker can exploit this remotely without requiring authentication or user interaction, by sending maliciously crafted data URIs that trigger the inefficient regex evaluation. The vulnerability does not compromise confidentiality, integrity, or availability directly but can degrade service availability by exhausting server resources, potentially leading to denial of service conditions. The vulnerability has been publicly disclosed, and a patch identified by commit 4454ebbdc7719016bf80ca0f34859ce5cee9f6b0 is available to remediate the issue. The CVSS 4.0 score is 5.3, reflecting a medium severity level, with an attack vector of network, low attack complexity, no privileges or user interaction required, and limited impact on availability. No known exploits are currently observed in the wild, but the public disclosure increases the risk of exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 00:02 UTC

Technical details

References

Community reviews

Related threats