CVE-2026-33013: Micronaut vulnerable to DoS via crafted form-urlencoded body binding with descending array indices

Published Mar 17, 2026
·
Updated

In JsonBeanPropertyBinder::expandArrayToThreshold in io.micronaut:micronaut-json-core before Micronaut 4 4.10.16 and in Micronaut 3 before 3.10.5 does not correctly handle descending array index order during form-urlencoded body binding, which allows remote attackers to cause a denial of service (non-terminating loop, CPU exhaustion, and OutOfMemoryError) via crafted indexed form parameters (e.g., authors[1].name followed by authors[0].name).

Example

With such an application

java package dosform;

import io.micronaut.http.HttpResponse; import io.micronaut.http.MediaType; import io.micronaut.http.annotation.Body; import io.micronaut.http.annotation.Consumes; import io.micronaut.http.annotation.Controller; import io.micronaut.http.annotation.Get; import io.micronaut.http.annotation.Post; import io.micronaut.http.annotation.Produces;

import java.net.URI;

@Controller class HomeController {

@Produces(MediaType.TEXTHTML) @Get String index() { return """ <!DOCTYPE html> <html> <head> <title></title> </head> <body> <form action="/submit" method="post"> <label for="firstAuthor">Fist Author</label> <input id="firstAuthor" name="authors[0].name" type="text"/>

<label for="secondAuthor">Second Author</label> <input id="secondAuthor" name="authors[1].name" type="text"/> <label for="thirdAuthor">Third Author</label> <input id="thirdAuthor" name="authors[2].name" type="text"/>

<button type="submit">Submit</button> </form> </body> </html> """; }

@Consumes(MediaType.APPLICATIONFORMURLENCODED) @Post("/submit") HttpResponse<?> submit(@Body Book book) { return HttpResponse.seeOther(URI.create("/")); } } package dosform;

import io.micronaut.core.annotation.Introspected;

import java.util.Objects;

@Introspected public class Author { private String name; public String getName() { return name; } public void setName(String name) { this.name = name; }

@Override public final boolean equals(Object o) { if (!(o instanceof Author)) return false;

Author author = (Author) o; return Objects.equals(name, author.name); }

@Override public int hashCode() { return Objects.hashCode(name); }

@Override public String toString() { return "Author{" + "name='" + name + '\'' + '}'; } } package dosform;

import io.micronaut.core.annotation.Introspected;

import java.util.List; import java.util.Objects;

@Introspected public class Book { private List<Author> authors; public List<Author> getAuthors() { return authors; } public void setAuthors(List<Author> authors) { this.authors = authors; }

@Override public final boolean equals(Object o) { if (!(o instanceof Book)) return false;

Book book = (Book) o; return Objects.equals(authors, book.authors); }

@Override public int hashCode() { return Objects.hashCode(authors); }

@Override public String toString() { return "Book{" + "authors=" + authors + '}'; } }

Sending curl -v -X POST 'http://127.0.0.1:8080/submit' -H 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'authors[1].name=RobertGalbraith' --data-urlencode 'authors[0].name=JKRowling' causes sustained CPU usage and unbounded memory growth (eventually OutOfMemoryError).

Patches For Micronaut 4, the problem has been patched in micronaut-core, dependencies with group id io.micronaut, since 4.10.16.

For Micronaut 3, the problem has been patched since 3.10.5

Users upgrade to the latest version of the framework.

Workarounds There is no way for users to fix or remediate the vulnerability without upgrading.

References PR Fix: https://github.com/micronaut-projects/micronaut-core/pull/12410

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
maven/io.micronaut:micronaut-json-core<3.10.5
3.10.5
maven/io.micronaut:micronaut-json-core>=4.0.0-M1<4.10.16
4.10.16
Objectcomputing Micronaut<3.10.5
Objectcomputing Micronaut>=4.0.0<4.10.16

Event History

Mar 17, 2026
Advisory Published
via GitHub·04:59 PM
Data Sourced
via GitHub·04:59 PM
DescriptionWeaknessAffected Software
Mar 20, 2026
CVE Published
via MITRE·04:47 AM
Data Sourced
via MITRE·04:47 AM
DescriptionWeakness
Data Sourced
via NVD·05:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33013?

CVE-2026-33013 has a severity rating of high with a CVSS score of 8.2.

2

How do I fix CVE-2026-33013?

To fix CVE-2026-33013, you should apply the latest patch available for Micronaut according to the remediation guidance.

3

What type of vulnerability is CVE-2026-33013?

CVE-2026-33013 is a denial of service (DoS) vulnerability that affects the binding of form-urlencoded bodies.

4

Which versions of Micronaut are affected by CVE-2026-33013?

CVE-2026-33013 affects Micronaut versions before 4.10.16 and 3.x versions before 3.10.5.

5

What impact does CVE-2026-33013 have on applications?

CVE-2026-33013 can allow remote attackers to cause a denial of service, negatively impacting application availability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203