How severe is CVE-2025-9624?

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

Which packages are affected by CVE-2025-9624?

CVE-2025-9624 affects the following packages: org.opensearch:opensearch-common (Maven), org.opensearch:opensearch-common (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-9624?

Update org.opensearch:opensearch-common to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9624 is resolved across your whole dependency graph.

How do I detect CVE-2025-9624 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch:opensearch-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-9624 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-9624 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-9624?

CVE-2025-9624 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-9624?

CVE-2025-9624 is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-9624 published, and has it been updated?

CVE-2025-9624 was published on November 25, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-9624 — opensearch-common

Fix: opensearch-project/OpenSearch#19491

CVE-2025-9624 is a CWE-674 vulnerability in org.opensearch:opensearch-common. A fix is available for org.opensearch:opensearch-common — see the affected versions and patch details below.

OpenSearch 3.2.0 - Nested Boolean/Disjunction asymmetric DoS

Also known asGHSA-mw3v-mmfw-3x2g

Published

Nov 25, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-9624.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.opensearch:opensearch-common☕org.opensearch:opensearch-common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability in OpenSearch allows attackers to cause Denial of Service (DoS) by submitting complex query_string inputs.

This issue affects all OpenSearch versions between 3.0.0 and < 3.3.0 and OpenSearch < 2.19.4.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opensearch:opensearch-common`	≥ 3.0.0&&< 3.3.0	3.3.0`org.opensearch:opensearch-common:3.3.0`
☕Maven	`org.opensearch:opensearch-common`	all versions	2.19.4`org.opensearch:opensearch-common:2.19.4`

Affected Products

1 product · 1 configurations

Application

opensearchamazon

< 3.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch:opensearch-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opensearch:opensearch-common to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9624 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

A vulnerability in OpenSearch allows attackers to cause Denial of Service (DoS) by submitting complex query_string inputs. This issue affects all OpenSearch versions between 3.0.0 and < 3.3.0 and OpenSearch < 2.19.4.

O3 Security · Impact-Aware SCA

Is CVE-2025-9624 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works