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

Advisory record · `GHSA-f2wh-grmh-r6jm`

- **Identifiers:** `GHSA-f2wh-grmh-r6jm` · `CVE-2026-41409`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 27 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Apr 2026, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.mina:mina-core` (Maven): affected `>=2.0.0, <2.0.28 || >=2.1.0, <2.1.11 || >=2.2.0, <2.2.6`; fixed in `2.0.28`, `2.1.11`, `2.2.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache MINA mina-core versions 2.0.0 through 2.0.27, 2.1.0 through 2.1.10, and 2.2.0 through 2.2.5 are affected. The incomplete fix for CVE-2024-52046 allowed a static initializer in a class to run before the classname allowlist was applied during deserialization in IoBuffer.getObject(), so applications calling that method may be exposed to attacks on untrusted data. Upgrade mina-core to 2.0.28, 2.1.11, or 2.2.6, matching your release line.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 38th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f2wh-grmh-r6jm)

## Sources

- [GitHub Advisory Database: GHSA-f2wh-grmh-r6jm](https://github.com/advisories/GHSA-f2wh-grmh-r6jm)
- [OSV: GHSA-f2wh-grmh-r6jm](https://osv.dev/vulnerability/GHSA-f2wh-grmh-r6jm)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41409>
- <https://github.com/advisories/GHSA-76h9-2vwh-w278>
- <https://github.com/apache/mina>
- <https://lists.apache.org/thread/9ddvsq6c4l5bhwq8l14sob4f8qjvx5c9>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f2wh-grmh-r6jm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f2wh-grmh-r6jm/>. Everything for agents: <https://agentprime.io/llms.txt>.
