Skip to content

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

Moderate severity GitHub Reviewed Published Jun 1, 2026 in micronaut-projects/micronaut-core

Package

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

Affected versions

>= 1.2.8, < 3.10.6
>= 4.0.0-M1, < 4.10.24
>= 5.0.0-M1, < 5.0.1

Patched versions

3.10.6
4.10.24
5.0.1

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: micronaut-projects/micronaut-core@9770328
Micronaut 4 Patch: micronaut-projects/micronaut-core@70cab4b
Micronaut 3 Patch: micronaut-projects/micronaut-core@64e5397

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

Severity

Moderate

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
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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:H/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS score

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-q6gh-6v2r-hjv3

Source code

Credits

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