micronaut-core: Loop with Unreachable Exit Condition
CVE-2026-33013 is a high-severity loop with unreachable exit condition vulnerability in micronaut-core from Micronaut-projects, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected micronaut-core versions: >= 4.0.0-M1, < 4.10.16; < 3.10.5. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Micronaut to 3.10.5 or 4.10.16, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Micronaut-projects | micronaut-core | >= 4.0.0-M1, < 4.10.16; < 3.10.5 | Not stated |
| Objectcomputing | Micronaut | before 3.10.5; 4.0.0 up to, but not including, 4.10.16 | 3.10.5, 4.10.16 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.2 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Loop with Unreachable Exit Condition
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
More Loop with Unreachable Exit Condition vulnerabilities (CWE-835)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- github.com/micronaut-projects/micronaut-core/commit/1afe509677c51b320041b7a2c177366d4a4deb55
- github.com/micronaut-projects/micronaut-core/pull/12410Issue Tracking
- github.com/micronaut-projects/micronaut-core/releases/tag/v3.10.5Release Notes
- github.com/micronaut-projects/micronaut-core/releases/tag/v4.10.16Release Notes
Other vulnerabilities in micronaut-core
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
Recent Loop with Unreachable Exit Condition vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.