NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Apache MINA vulnerable to Deserialization of Untrusted DataGHSA-8297-v2rf-2p32

CRITICAL

GHSA-8297-v2rf-2p32 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.

Also known asCVE-2026-41635
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-8297-v2rf-2p32.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk
0.00%0.44%0.88%1.32%0.1%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

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

Apache MINA's AbstractIoBuffer.resolveClass() contains two branches, one of them (for static classes or primitive types) does not check the class at all, bypassing the classname allowlist and allowing arbitrary code to be executed.

The fix checks if the class is present in the accepted class filter before calling Class.forName(). 

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
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.mina:mina-core≥ 2.0.0&&< 2.0.282.0.28org.apache.mina:mina-core:2.0.28
☕Mavenorg.apache.mina:mina-core≥ 2.1.0&&< 2.1.112.1.11org.apache.mina:mina-core:2.1.11
☕Mavenorg.apache.mina:mina-core≥ 2.2.0&&< 2.2.62.2.6org.apache.mina:mina-core:2.2.6

Affected Products

1 product · 3 configurations
Application
minaapache
≥ 2.2.0 && < 2.2.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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-8297-v2rf-2p32 is resolved across your whole dependency graph.

  3. 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 HatLow

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.

ProductFixed inAdvisory
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14mina-coreRHSA-2026:17668
OpenShift Developer Tools and Services 4.12ocp-tools-4/jenkins-rhel8:1786628667RHSA-2026:60247
OpenShift Developer Tools and Services 4.13ocp-tools-4/jenkins-rhel8:1786628681RHSA-2026:60249
OpenShift Developer Tools and Services 4.14ocp-tools-4/jenkins-rhel8:1786533561RHSA-2026:60248
OpenShift Developer Tools and Services 4.15ocp-tools-4/jenkins-rhel8:1786533565RHSA-2026:60239
OpenShift Developer Tools and Services 4.16ocp-tools-4/jenkins-rhel9:1787125166RHSA-2026:60251
OpenShift Developer Tools and Services 4.17ocp-tools-4/jenkins-rhel9:1787124635RHSA-2026:60246
OpenShift Developer Tools and Services 4.18ocp-tools-4/jenkins-rhel9:1787125069RHSA-2026:60250

Frequently Asked Questions

Apache MINA's AbstractIoBuffer.resolveClass() contains two branches, one of them (for static classes or primitive types) does not check the class at all, bypassing the classname allowlist and allowing arbitrary code to be executed. The fix checks if the class is present in the accepted class filter before calling Class.forName().  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.ge
O3 Security · Impact-Aware SCA

Is GHSA-8297-v2rf-2p32 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache MINA vulnerable to Deserialization of Untrusted…