# CVE-2026-94301: Apache MINA: CVE-2026-47065 resolveProxyClass fix missing from 2.0.X and 2.1.X branches (2.0.30 / 2.1.14) ZDRES-232


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-h355-27x9-rr7r, UBUNTU-CVE-2026-94301

## What is CVE-2026-94301?

CVE-2026-94301 is a critical vulnerability in Apache MINA, published on 21 Sep 2026. 

### Official description

The fix for CVE-2026-47065/ZDRES-232 ("resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy"), released on 2026-06-02 and announced as "Fully addressed" in MINA 2.2.8, 2.1.13 and 2.0.29, was committed to the
 2.2.X branch only. The 2.0.X and 2.1.X maintenance branches never received the resolveProxyClass() override, so the 2.0.29 and 2.1.13 artifacts listed as fixed -- and every later release on those lines, up to and including the current 2.0.30 and 2.1.14 -- remain vulnerable to the exact allow-list bypass that CVE-2026-47065 was meant to close.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-94301?


## How do I fix CVE-2026-94301?

No fix has been published for CVE-2026-94301 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-94301 being exploited?

There is no known exploitation of CVE-2026-94301 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94301 and fix it if it is affected.

What it is: CVE-2026-94301 is a critical vulnerability in Apache MINA, published on 21 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-94301 in the wild and no public exploit code.

Affected product: Apache MINA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94301/ (Markdown: https://insights.sbomify.com/CVE-2026-94301/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94301
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94301
- OSV: https://osv.dev/vulnerability/CVE-2026-94301

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94301/
Summaries are generated and may contain mistakes; the official description above is the record.