GHSA-v3pr-hxpr-mfm8 — mina-core
CRITICALGHSA-v3pr-hxpr-mfm8 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.mina:mina-core. A fix is available for org.apache.mina:mina-core — see the affected versions and patch details below.
Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v3pr-hxpr-mfm8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-v3pr-hxpr-mfm8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,066 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.mina:mina-core☕org.apache.mina:mina-core☕org.apache.mina:mina-coreReal-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
ZDRES-232: resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy
Assessment: Fully addressed.
When the serialised stream contains a TC_PROXYCLASSDESC (the marker for a java.lang.reflect.Proxy ), JDK’s ObjectInputStream.readProxyDesc() is dispatched. JDK then calls the default ObjectInputStream.resolveProxyClass(interfaces) implementation, which performs Class.forName(intf, false, latestUserDefinedLoader()) for EACH interface name and constructs the proxy class — bypassing the accepted classes list .
ZDRES-233: Class.forName(name, initialize=true, classLoader) in readClassDescriptor Triggers Static Initialiser of Allow-Listed Classes
Assessment: Fully addressed.
For ANY class on the allow-list, deserialising a stream that names it triggers the class’s (static initialiser) BEFORE any instance is constructed. This means an attacker who supplies a class name on the allow-list (e.g., the developer wrote accept(“com.myapp.*") , attacker supplies com.myapp.SomeClass ) causes <clinit> of SomeClass — and many real-world classes have side-effecting static initialisers
Both issues have been fixed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.mina:mina-core | ≥ 2.2.0&&< 2.2.8 | 2.2.8org.apache.mina:mina-core:2.2.8 |
| ☕Maven | org.apache.mina:mina-core | ≥ 2.1.0&&< 2.1.13 | 2.1.13org.apache.mina:mina-core:2.1.13 |
| ☕Maven | org.apache.mina:mina-core | all versions | 2.0.29org.apache.mina:mina-core:2.0.29 |
Affected Products
minaapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mina:mina-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.mina:mina-core to 2.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3pr-hxpr-mfm8 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat products are affected by this vulnerability. However, the vulnerable code cannot be reached and therefore are not vulnerable. Due to this reason, this flaw has been rated with a low severity.
| Product | Fixed in | Advisory |
|---|---|---|
| OpenShift Developer Tools and Services 4.12 | ocp-tools-4/jenkins-rhel8:1786628667 | RHSA-2026:60247 |
| OpenShift Developer Tools and Services 4.13 | ocp-tools-4/jenkins-rhel8:1786628681 | RHSA-2026:60249 |
| OpenShift Developer Tools and Services 4.14 | ocp-tools-4/jenkins-rhel8:1786533561 | RHSA-2026:60248 |
| OpenShift Developer Tools and Services 4.15 | ocp-tools-4/jenkins-rhel8:1786533565 | RHSA-2026:60239 |
| OpenShift Developer Tools and Services 4.16 | ocp-tools-4/jenkins-rhel9:1787125166 | RHSA-2026:60251 |
| OpenShift Developer Tools and Services 4.17 | ocp-tools-4/jenkins-rhel9:1787124635 | RHSA-2026:60246 |
| OpenShift Developer Tools and Services 4.18 | ocp-tools-4/jenkins-rhel9:1787125069 | RHSA-2026:60250 |
| OpenShift Developer Tools and Services 4.19 | ocp-tools-4/jenkins-rhel9:1787124632 | RHSA-2026:60252 |
Frequently Asked Questions
Is GHSA-v3pr-hxpr-mfm8 in your dependencies?
Find it across Maven, including transitive dependencies.