Apache MINA Corrects an Incomplete Deserialization Fix
Tech GuruQuick Answer
Apache MINA's earlier deserialization fix did not reach the 2.0 and 2.1 maintenance branches as announced. For CVE-2026-94301, use 2.0.31 on the 2.0 line or 2.1.15 on the 2.1 line. Versions 2.0.29/2.0.30 and 2.1.13/2.1.14 remain affected despite the earlier fix claim.
Confirm Scope And Apply The Supported Fix
What to do now: Check the MINA artifact actually deployed, including bundled dependencies. Reopen any remediation record that accepted 2.0.29 or 2.1.13 as closing the proxy-class allow-list bypass, then install and verify the corrected maintenance release.
Last verified: 2026-09-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Apache MINA 2.0.x before 2.0.31 and 2.1.x before 2.1.15 |
|---|---|
| Advisory | CVE-2026-94301 |
| CVE | CVE-2026-94301 |
| CVE record publication | 2026-09-21 14:35:59.952 UTC |
| Recorded source revision (historical snapshot) | 2026-09-21 15:38:00.430 UTC |
| Affected versions | Apache MINA 2.0.x before 2.0.31 and 2.1.x before 2.1.15 |
| Fixed version | Apache MINA 2.0.31 / 2.1.15 |
| CVSS base score | 9.8 (CVSS v3.1) |
| CVSS severity | Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The June 2 fix for CVE-2026-47065/ZDRES-232 was announced for 2.2.8, 2.1.13, and 2.0.29, but the resolveProxyClass() override was committed only to 2.2.X. Without it, proxy-class deserialization can bypass the acceptMatchers allow-list via java.lang.reflect.Proxy. The correction is therefore branch-specific: the affected intervals are 2.0.0 through before 2.0.31 and 2.1.0 through before 2.1.15.
What To Validate Now
- Inventory. Record the resolved MINA branch/version in running application artifacts and the components that use its deserialization path; do not rely only on the declared dependency in a build file.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Apache MINA 2.0.x before 2.0.31 and 2.1.x before 2.1.15 Do not infer applicability from product family or severity alone.
- Remediate. Apply Apache MINA 2.0.31 / 2.1.15 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the corrected branch release in the deployed artifact and run approved serialization/filter regression tests in the application's test environment. Do not accept the earlier fixed-version announcement as proof the maintenance-branch patch was present.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
