Skip to content

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

High severity GitHub Reviewed Published Jun 1, 2026 in micronaut-projects/micronaut-core • Updated Jul 9, 2026

Package

maven io.micronaut:micronaut-http-client (Maven)

Affected versions

< 3.10.7
>= 4.0.0-M1, < 4.10.24
>= 5.0.0-M1, < 5.0.1

Patched versions

3.10.7
4.10.24
5.0.1

Description

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: micronaut-projects/micronaut-core@6e88a97
Micronaut 4 Patch: micronaut-projects/micronaut-core@f1dffff
Micronaut 3 Patch: micronaut-projects/micronaut-core@c06a271

References

@sdelamo sdelamo published to micronaut-projects/micronaut-core Jun 1, 2026
Published to the GitHub Advisory Database Jul 9, 2026
Reviewed Jul 9, 2026
Last updated Jul 9, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-387m-935m-c4vw

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.