GHSA-Q6GH-6V2R-HJV3

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

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

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

GHSA-Q6GH-6V2R-HJV3 has a CVSS score of 6.8 (Medium). 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.6, 4.10.24, 5.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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

1. What is GHSA-Q6GH-6V2R-HJV3? GHSA-Q6GH-6V2R-HJV3 is a medium-severity security vulnerability in io.micronaut:micronaut-http-client (maven), affecting versions >= 1.2.8, < 3.10.6. It is fixed in 3.10.6, 4.10.24, 5.0.1.
2. How severe is GHSA-Q6GH-6V2R-HJV3? GHSA-Q6GH-6V2R-HJV3 has a CVSS score of 6.8 (Medium). 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.
3. Which versions of io.micronaut:micronaut-http-client are affected by GHSA-Q6GH-6V2R-HJV3? io.micronaut:micronaut-http-client (maven) versions >= 1.2.8, < 3.10.6 is affected.
4. Is there a fix for GHSA-Q6GH-6V2R-HJV3? Yes. GHSA-Q6GH-6V2R-HJV3 is fixed in 3.10.6, 4.10.24, 5.0.1. Upgrade to this version or later.
5. Is GHSA-Q6GH-6V2R-HJV3 exploitable, and should I be worried? Whether GHSA-Q6GH-6V2R-HJV3 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
6. What actually determines whether GHSA-Q6GH-6V2R-HJV3 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.
7. How do I fix GHSA-Q6GH-6V2R-HJV3?
   • Upgrade io.micronaut:micronaut-http-client to 3.10.6 or later
   • Upgrade io.micronaut:micronaut-http-client to 4.10.24 or later
   • Upgrade io.micronaut:micronaut-http-client to 5.0.1 or later

Other vulnerabilities in io.micronaut:micronaut-http-client