# GHSA-387m-935m-c4vw: Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS

> An attacker can cause a denial of service by triggering an infinite redirect loop in the Micronaut HTTP Client due to missing redirect limits.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026

## What is GHSA-387m-935m-c4vw?

GHSA-387m-935m-c4vw is a denial of service vulnerability in io.micronaut:micronaut-http-client, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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](https://github.com/micronaut-projects/micronaut-core/releases/v5.0.1) >=
- For Micronaut 4, versions equal or greater than [4.10.24](https://github.com/micronaut-projects/micronaut-core/releases/v4.10.24) >=
- For Micronaut 3, versions equal or greater than [3.10.7](https://github.com/micronaut-projects/micronaut-core/releases/v3.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

## Which versions are affected by GHSA-387m-935m-c4vw?

6 open source packages ship an affected version, including io.micronaut:micronaut-http-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.micronaut:micronaut-http-client` | Maven | All versions | 3.10.7 |
| `io.micronaut:micronaut-http-client` | Maven | All versions | 3.10.7 |
| `io.micronaut:micronaut-http-client` | Maven | From 4.0.0-M1 | 4.10.24 |
| `io.micronaut:micronaut-http-client` | Maven | From 4.0.0-M1 | 4.10.24 |
| `io.micronaut:micronaut-http-client` | Maven | From 5.0.0-M1 | 5.0.1 |
| `io.micronaut:micronaut-http-client` | Maven | From 5.0.0-M1 | 5.0.1 |

## How do I fix GHSA-387m-935m-c4vw?

Upgrade io.micronaut:micronaut-http-client to a fixed version for your release line: 3.10.7, 4.10.24 or 5.0.1.

## Is GHSA-387m-935m-c4vw being exploited?

There is no known exploitation of GHSA-387m-935m-c4vw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-387m-935m-c4vw and fix it if it is affected.

What it is: GHSA-387m-935m-c4vw is a denial of service vulnerability in io.micronaut:micronaut-http-client, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-387m-935m-c4vw in the wild and no public exploit code.

Affected packages and fixed versions:
- io.micronaut:micronaut-http-client (Maven): affected all versions; fixed in 3.10.7
- io.micronaut:micronaut-http-client (Maven): affected all versions; fixed in 3.10.7
- io.micronaut:micronaut-http-client (Maven): affected from 4.0.0-M1; fixed in 4.10.24
- io.micronaut:micronaut-http-client (Maven): affected from 4.0.0-M1; fixed in 4.10.24
- io.micronaut:micronaut-http-client (Maven): affected from 5.0.0-M1; fixed in 5.0.1
- io.micronaut:micronaut-http-client (Maven): affected from 5.0.0-M1; fixed in 5.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-387m-935m-c4vw/ (Markdown: https://insights.sbomify.com/GHSA-387m-935m-c4vw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-387m-935m-c4vw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-387m-935m-c4vw/
Summaries are generated and may contain mistakes; the official description above is the record.