CVE-2026-33013: Micronaut Framework is a JVM-based full stack Java framework designed for building modular, easily testable JV

This week

HIGH 7.5REMOTEUPGRADE

CVE-2026-33013 is a high-severity flaw (CVSS 7.5) affecting micronaut. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 paramete

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-835
Published	2026-03-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: objectcomputing

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-20 05:16 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

objectcomputing micronaut UPGRADE

Affected: < 3.10.5 · >= 4.0.0 and < 4.10.16

Fixed in: 3.10.5, 4.10.16

Safe to downgrade to: a release before 4.0.0

1. Check installed version

apt-cache policy micronaut || rpm -q micronaut || micronaut --version

2. UPGRADE to 3.10.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade micronaut

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade micronaut

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)

apt-cache madison micronaut sudo apt install micronaut=<VERSION_BEFORE_4.0.0> sudo apt-mark hold micronaut

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list micronaut sudo dnf downgrade micronaut-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add micronaut

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33013?

micronaut: upgrade to 3.10.5, 4.10.16. Exact commands for each OS are on this page.

Is CVE-2026-33013 being exploited?

CVE-2026-33013 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33013 affect?

CVE-2026-33013 affects micronaut. Severity is high (CVSS 7.5). 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-urlenco

How urgent is CVE-2026-33013?

Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-33012 HIGH 7.5 UPGRADE Micronaut Framework is a JVM-based full stack Java framework designed for building modular, easily testable JV

References

← Back to latest CVEs