How severe is GHSA-f2wh-grmh-r6jm?

GHSA-f2wh-grmh-r6jm has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-f2wh-grmh-r6jm?

GHSA-f2wh-grmh-r6jm affects the following packages: org.apache.mina:mina-core (Maven), org.apache.mina:mina-core (Maven), org.apache.mina:mina-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f2wh-grmh-r6jm?

Update org.apache.mina:mina-core to 2.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2wh-grmh-r6jm is resolved across your whole dependency graph.

How do I detect GHSA-f2wh-grmh-r6jm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mina:mina-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f2wh-grmh-r6jm 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.

How does O3 Security protect against GHSA-f2wh-grmh-r6jm?

O3 pinpoints whether GHSA-f2wh-grmh-r6jm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f2wh-grmh-r6jm actively exploited in the wild?

No public exploit code has been indexed for GHSA-f2wh-grmh-r6jm 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 GHSA-f2wh-grmh-r6jm?

GHSA-f2wh-grmh-r6jm has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th 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.

When was GHSA-f2wh-grmh-r6jm published, and has it been updated?

GHSA-f2wh-grmh-r6jm was published on April 27, 2026 and was last updated on May 7, 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

GHSA-f2wh-grmh-r6jm

CRITICAL

GHSA-f2wh-grmh-r6jm is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.apache.mina:mina-core. O3 Security confirms whether GHSA-f2wh-grmh-r6jm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache MINA Vulnerable to Deserialization of Untrusted Data (CVE-2024-52046 Incomplete Fix)

Also known asCVE-2026-41409

Published

Apr 27, 2026

Updated

May 7, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk36th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

☕org.apache.mina:mina-core☕org.apache.mina:mina-core☕org.apache.mina:mina-core

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

Affected versions are Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, and 2.2.0 <= 2.2.5.

The problem is resolved in Apache MINA 2.0.28, 2.1.11, and 2.2.6 by applying the classname allowlist earlier.

Affected are applications using Apache MINA that call IoBuffer.getObject().

Applications using Apache MINA are advised to upgrade

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.mina:mina-core`	≥ 2.0.0&&< 2.0.28	2.0.28
☕Maven	`org.apache.mina:mina-core`	≥ 2.1.0&&< 2.1.11	2.1.11
☕Maven	`org.apache.mina:mina-core`	≥ 2.2.0&&< 2.2.6	2.2.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mina:mina-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.mina:mina-core to 2.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2wh-grmh-r6jm is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-f2wh-grmh-r6jm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f2wh-grmh-r6jm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, and 2.2.0 <= 2.2.5. The problem is resolved in Apache MINA 2.0.28, 2.1.11, and 2.2.6 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade

O3 Security · Impact-Aware SCA

Is GHSA-f2wh-grmh-r6jm in your dependencies?

O3 detects GHSA-f2wh-grmh-r6jm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works