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

This month

HIGH 7.5REMOTEUPGRADE

CVE-2026-33012 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 4.7.0 through 4.10.16 used an unbounded ConcurrentHashMap cache with no eviction policy in its DefaultHtmlErrorResponseBodyProvider. If the application throws an exception whose message may be influenced by an attacker, (for example, including request query value parameters) it could be used by remote attackers t

Why this priority

High severity
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 53%)
CISA exploited list	No
Weakness	CWE-770
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: >= 4.7.0 and < 4.10.17

Fixed in: 4.10.17

Safe to downgrade to: a release before 4.7.0

1. Check installed version

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

2. UPGRADE to 4.10.17 (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.7.0 (Debian / Ubuntu)

apt-cache madison micronaut sudo apt install micronaut=<VERSION_BEFORE_4.7.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.7.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-33012?

micronaut: upgrade to 4.10.17. Exact commands for each OS are on this page.

Is CVE-2026-33012 being exploited?

CVE-2026-33012 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-33012 affect?

CVE-2026-33012 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 4.7.0 through 4.10.16 used an unbounded ConcurrentHashMap cache with no eviction policy in its DefaultHt

How urgent is CVE-2026-33012?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-33013 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