Micronaut: DefaultHttpClient follows redirects, forwarding Authorization, Cookie, and Proxy-Authorization headers

Exploitation

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

CVSS

6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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:…

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

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

# Patch Next advisory brief: GHSA-q6gh-6v2r-hjv3

Advisory: Micronaut: DefaultHttpClient follows redirects, forwarding Authorization, Cookie, and Proxy-Authorization headers
IDs: GHSA-q6gh-6v2r-hjv3
Record: https://patchnext.com/advisories/ghsa-q6gh-6v2r-hjv3 (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: Medium (CVSS 6.8)
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.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.micronaut:micronaut-http-client: affected >= 1.2.8, < 3.10.6; >= 4.0.0-M1, < 4.10.24; >= 5.0.0-M1, < 5.0.1; fixed in 5.0.1, 3.10.6, 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-q6gh-6v2r-hjv3 (GitHub-reviewed advisory GHSA-q6gh-6v2r-hjv3 lists affected ranges: Maven io.micronaut:micronaut-http-client >=1.2.8 =4.0.0-M1 =5.0.0-M1 <5.0.1)

Commands are suggestions: review each one before running it.