# GHSA-q6gh-6v2r-hjv3: Micronaut: DefaultHttpClient follows redirects, forwarding Authorization, Cookie, and Proxy-Authorization headers

> Micronaut DefaultHttpClient leaks sensitive headers to cross-domain redirect targets and allows infinite redirect loops, risking credential exposure and DoS.

- **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-q6gh-6v2r-hjv3?

GHSA-q6gh-6v2r-hjv3 is a 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

### Impact

> DefaultHttpClient follows redirects and forwards Authorization, Cookie, and Proxy-Authorization headers to redirect targets across domain boundaries. The blocklist only filters Host/Connection/TE/CT/CL.
> Additionally, no maximum redirect count exists, enabling infinite loop DoS.
> Affected: DefaultHttpClient.java lines 231-245, 1591, 2071

> Suggested fix: Strip sensitive headers on cross-domain redirects

### Patches
It has been patched for versions: 

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.6 >=

### Workarounds
No

### References
Micronaut 5 Patch: https://github.com/micronaut-projects/micronaut-core/commit/9770328999f490bdfbb9e25addd45bf73d4a173a
Micronaut 4 Patch: https://github.com/micronaut-projects/micronaut-core/commit/70cab4b44fbf985faba2846091f2356b5bd70719
Micronaut 3 Patch: https://github.com/micronaut-projects/micronaut-core/commit/64e539736b8168f201d868b02ace50fe14f57418

## Which versions are affected by GHSA-q6gh-6v2r-hjv3?

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 | From 1.2.8 | 3.10.6 |
| `io.micronaut:micronaut-http-client` | Maven | From 1.2.8 | 3.10.6 |
| `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-q6gh-6v2r-hjv3?

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

## Is GHSA-q6gh-6v2r-hjv3 being exploited?

There is no known exploitation of GHSA-q6gh-6v2r-hjv3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q6gh-6v2r-hjv3 and fix it if it is affected.

What it is: GHSA-q6gh-6v2r-hjv3 is a 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-q6gh-6v2r-hjv3 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.micronaut:micronaut-http-client (Maven): affected from 1.2.8; fixed in 3.10.6
- io.micronaut:micronaut-http-client (Maven): affected from 1.2.8; fixed in 3.10.6
- 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-q6gh-6v2r-hjv3/ (Markdown: https://insights.sbomify.com/GHSA-q6gh-6v2r-hjv3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q6gh-6v2r-hjv3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q6gh-6v2r-hjv3/
Summaries are generated and may contain mistakes; the official description above is the record.