CVE-2026-33013
Objectcomputing Micronaut denial of service
- Published20 Mar 2026
Description
Micronaut Framework is a JVM-based full stack Java framework designed for building modular, easily testable JVM applications. Versions prior to both 4.10.16 and 3.10.5 do not correctly handle descending array index order during form-urlencoded body binding in theJsonBeanPropertyBinder::expandArrayToThreshold, which allows remote attackers to cause a DoS (non-terminating loop, CPU exhaustion, and OutOfMemoryError) via crafted indexed form parameters (e.g., authors[1].name followed by authors[0].name). This issue has been fixed in versions 4.10.16 and 3.10.5.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
References
- https://github.com/micronaut-projects/micronaut-core/commit/1afe509677c51b320041b7a2c177366d4a4deb55
- https://github.com/micronaut-projects/micronaut-core/pull/12410
- https://github.com/micronaut-projects/micronaut-core/releases/tag/v3.10.5
- https://github.com/micronaut-projects/micronaut-core/releases/tag/v4.10.16
- https://github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-43w5-mmxv-cpvh
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-33013 being actively exploited?
CVE-2026-33013 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.78%.
How severe is CVE-2026-33013?
CVE-2026-33013 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.78% probability of exploitation.
Which products are affected by CVE-2026-33013?
Affected products include Objectcomputing Micronaut.
How do I fix CVE-2026-33013?
Upgrade affected software to a fixed version, for example Objectcomputing Micronaut 4.10.16 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-33013 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.