CVE-2026-42778

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The fix for CVE-2026-41409 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description:

The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed.

Affected versions are Apache MINA 2.1.0 <= 2.1.11, and 2.2.0 <= 2.2.6.

The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier.

Affected are applications using Apache MINA that call IoBuffer.getObject().

Applications using Apache MINA are advised to upgrade

The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed.

Affected versions are Apache MINA 2.1.0 <= 2.1.110, and 2.2.0 <= 2.2.6.

The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier.

Affected are applications using Apache MINA that call IoBuffer.getObject().

Applications using Apache MINA are advised to upgrade

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 1, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread/fhlx5k91hrkgyzh7yk1nghrn3k27gxy0

Vendor Advisories for CVE-2026-42778(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.mina:mina-core2.2.0 ... 2.2.6 (7 versions)2.2.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 202 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-04 00:59 UTCOSV refresh
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 13:45 UTCEG score recompute
Show 75 more
  1. 2026-08-17 13:45 UTCVendor advisory
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 09:15 UTCVendor advisory
  4. 2026-08-16 05:19 UTCEG score recompute
  5. 2026-08-16 05:19 UTCVendor advisory
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:59 UTCEG score recompute
  8. 2026-08-15 01:59 UTCVendor advisory
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 22:18 UTCVendor advisory
  11. 2026-08-14 18:31 UTCVendor advisory
  12. 2026-08-14 14:50 UTCVendor advisory
  13. 2026-08-14 11:09 UTCVendor advisory
  14. 2026-08-14 07:28 UTCVendor advisory
  15. 2026-08-14 03:48 UTCEG score recompute
  16. 2026-08-14 03:48 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 08:23 UTCVendor advisory
  19. 2026-08-13 04:41 UTCVendor advisory
  20. 2026-08-13 01:01 UTCVendor advisory
  21. 2026-08-12 21:20 UTCVendor advisory
  22. 2026-08-12 17:25 UTCEG score recompute
  23. 2026-08-12 17:25 UTCVendor advisory
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 23:50 UTCVendor advisory
  26. 2026-08-11 20:09 UTCVendor advisory
  27. 2026-08-11 16:23 UTCEG score recompute
  28. 2026-08-11 16:23 UTCVendor advisory
  29. 2026-08-11 13:43 UTCEPSS rescore
  30. 2026-08-11 09:12 UTCVendor advisory
  31. 2026-08-11 05:31 UTCVendor advisory
  32. 2026-08-11 01:50 UTCEG score recompute
  33. 2026-08-11 01:50 UTCVendor advisory
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 12:45 UTCVendor advisory
  36. 2026-08-10 08:36 UTCVendor advisory
  37. 2026-08-10 04:55 UTCVendor advisory
  38. 2026-08-10 01:15 UTCVendor advisory
  39. 2026-08-09 21:34 UTCVendor advisory
  40. 2026-08-09 17:52 UTCVendor advisory
  41. 2026-08-09 14:12 UTCEG score recompute
  42. 2026-08-09 14:12 UTCVendor advisory
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-09 10:31 UTCVendor advisory
  45. 2026-08-09 06:40 UTCVendor advisory
  46. 2026-08-09 02:59 UTCEG score recompute
  47. 2026-08-09 02:59 UTCVendor advisory
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 10:24 UTCVendor advisory
  50. 2026-08-08 06:43 UTCVendor advisory
  51. 2026-08-08 03:02 UTCVendor advisory
  52. 2026-08-07 23:21 UTCVendor advisory
  53. 2026-08-07 19:40 UTCEG score recompute
  54. 2026-08-07 19:40 UTCVendor advisory
  55. 2026-08-07 16:00 UTCVendor advisory
  56. 2026-08-07 12:19 UTCVendor advisory
  57. 2026-08-07 02:35 UTCVendor advisory
  58. 2026-08-06 20:48 UTCVendor advisory
  59. 2026-08-06 17:07 UTCEG score recompute
  60. 2026-08-06 17:07 UTCVendor advisory
  61. 2026-08-06 13:46 UTCEPSS rescore
  62. 2026-08-06 13:21 UTCVendor advisory
  63. 2026-08-06 09:39 UTCVendor advisory
  64. 2026-08-06 05:58 UTCVendor advisory
  65. 2026-08-06 02:17 UTCVendor advisory
  66. 2026-08-05 22:36 UTCEG score recompute
  67. 2026-08-05 22:36 UTCVendor advisory
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-04 15:10 UTCEPSS rescore
  70. 2026-08-04 10:38 UTCEPSS rescore
  71. 2026-08-04 03:52 UTCVendor advisory
  72. 2026-08-04 00:07 UTCVendor advisory
  73. 2026-08-03 20:25 UTCEG score recompute
  74. 2026-08-03 20:25 UTCVendor advisory
  75. 2026-08-03 10:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-42778?
CVE-2026-42778 is a critical vulnerability published on May 1, 2026. The fix for CVE-2026-41409 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description: The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a…
When was CVE-2026-42778 disclosed?
CVE-2026-42778 was first published in the National Vulnerability Database on May 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42778 actively exploited?
CVE-2026-42778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.5% of all scored CVEs.
What is the CVSS score of CVE-2026-42778?
CVE-2026-42778 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-42778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42778, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42778

Explore →

Is Your Infrastructure Affected by CVE-2026-42778?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs