Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

The Netty-based Micronaut HTTP Client does not impose a limit on HTTP redirections, potentially allowing an infinite redirect loop that could lead to a denial-of-service attack. Patches The following versions are patched: - For Micronaut 5, versions equal or greater than 5.0.1 = - For Micronaut 4, versions equal or greater than 4.10.24 = - For Micronaut 3, versions equal or greater than 3.10.7 = Workarounds No Resources Micronaut 5 Patch: https://github.com/micronaut-projects/micronaut-core/commit/6e88a972718d6e1521c5b3bb7766451798dba4e3 Micronaut 4 Patch: https://github.com/micronaut-projects/micronaut-core/commit/f1dffffec8fb5e3b7e94ae907ce0be3831e499d4 Micronaut 3 Patch: https://github.com/micronaut-projects/micronaut-core/commit/c06a2715ca7f78321bc3ca05f41cca78cd351320

Published by the source

9 Jul 2026, 13:36 UTC

Last modified by the source

9 Jul 2026, 13:36 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-387m-935m-c4vw

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

# Patch Next advisory brief: GHSA-387m-935m-c4vw

Advisory: Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS
IDs: GHSA-387m-935m-c4vw
Record: https://patchnext.com/advisories/ghsa-387m-935m-c4vw (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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-client 5.0.1, 4.10.24, 3.10.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.micronaut:micronaut-http-client: affected < 3.10.7; >= 4.0.0-M1, < 4.10.24; >= 5.0.0-M1, < 5.0.1; fixed in 3.10.7, 5.0.1, 4.10.24

## Suggested inspection (read-only)
- Maven io.micronaut:micronaut-http-client: 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-client.
- 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-387m-935m-c4vw (GitHub-reviewed advisory GHSA-387m-935m-c4vw lists affected ranges: Maven io.micronaut:micronaut-http-client >=0 =4.0.0-M1 =5.0.0-M1 <5.0.1)

Commands are suggestions: review each one before running it.