Summary
Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS
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.
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
Impact
GHSA-387M-935M-C4VW has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.10.7, 4.10.24, 5.0.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The following versions are patched:
Frequently Asked Questions
- What is GHSA-387M-935M-C4VW? GHSA-387M-935M-C4VW is a high-severity security vulnerability in io.micronaut:micronaut-http-client (maven), affecting versions < 3.10.7. It is fixed in 3.10.7, 4.10.24, 5.0.1.
- How severe is GHSA-387M-935M-C4VW? GHSA-387M-935M-C4VW has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of io.micronaut:micronaut-http-client are affected by GHSA-387M-935M-C4VW? io.micronaut:micronaut-http-client (maven) versions < 3.10.7 is affected.
- Is there a fix for GHSA-387M-935M-C4VW? Yes. GHSA-387M-935M-C4VW is fixed in 3.10.7, 4.10.24, 5.0.1. Upgrade to this version or later.
- Is GHSA-387M-935M-C4VW exploitable, and should I be worried? Whether GHSA-387M-935M-C4VW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-387M-935M-C4VW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-387M-935M-C4VW?
- Upgrade
io.micronaut:micronaut-http-clientto 3.10.7 or later - Upgrade
io.micronaut:micronaut-http-clientto 4.10.24 or later - Upgrade
io.micronaut:micronaut-http-clientto 5.0.1 or later
- Upgrade