Memory leak in micronaut-core

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2022-21700: 1.15% estimated exploitation activity in the next 30 days; percentile 66.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Sending an invalid Content Type header leads to memory leak in DefaultArgumentConversionContext as this type is erroneously used in static state. Patches The problem is patched in Micronaut 3.2.7 and above. Workarounds The default content type binder can be replaced in an existing Micronaut application to mitigate the issue: References Commit that introduced the vulnerability https://github.com/micronaut-projects/micronaut-core/commit/b8ec32c311689667c69ae7d9f9c3b3a8abc96fe3 For more information If you have any questions or comments about this advisory: Open an issue in Micronaut Core Email us at info@micronaut.io

Published by the source

21 Jan 2022, 23:19 UTC

Last modified by the source

3 Feb 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2457-2263-mm9f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-21700

Advisory: Memory leak in micronaut-core
IDs: CVE-2022-21700, GHSA-2457-2263-mm9f
Record: https://patchnext.com/advisories/cve-2022-21700 (revision 1, source checked 26 Oct 2026, 16:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.micronaut:micronaut-http 3.2.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.micronaut:micronaut-http: affected < 3.2.7; fixed in 3.2.7

## Suggested inspection (read-only)
- Maven io.micronaut:micronaut-http: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.micronaut:micronaut-http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2457-2263-mm9f (GitHub-reviewed advisory GHSA-2457-2263-mm9f lists affected ranges: Maven io.micronaut:micronaut-http >=0 <3.2.7)

Commands are suggestions: review each one before running it.