How severe is GHSA-387m-935m-c4vw?

GHSA-387m-935m-c4vw has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-387m-935m-c4vw?

GHSA-387m-935m-c4vw affects the following packages: io.micronaut:micronaut-http-client (Maven), io.micronaut:micronaut-http-client (Maven), io.micronaut:micronaut-http-client (Maven). Ecosystems affected: Maven.

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

Update io.micronaut:micronaut-http-client to 3.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-387m-935m-c4vw is resolved across your whole dependency graph.

How do I detect GHSA-387m-935m-c4vw in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.micronaut:micronaut-http-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-387m-935m-c4vw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-387m-935m-c4vw actively exploited in the wild?

No public exploit code has been indexed for GHSA-387m-935m-c4vw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-387m-935m-c4vw published, and has it been updated?

GHSA-387m-935m-c4vw was published on July 9, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-387m-935m-c4vw — micronaut-http-client

HIGHFix: micronaut-projects/micronaut-core@6e88a97

GHSA-387m-935m-c4vw is a high-severity (CVSS 7.5) vulnerability in io.micronaut:micronaut-http-client. A fix is available for io.micronaut:micronaut-http-client — see the affected versions and patch details below.

Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS

Published

Jul 9, 2026

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

☕io.micronaut:micronaut-http-client☕io.micronaut:micronaut-http-client☕io.micronaut:micronaut-http-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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 >=
For Micronaut 4, versions equal or greater than 4.10.24 >=
For Micronaut 3, versions equal or greater than 3.10.7 >=

Workarounds

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.micronaut:micronaut-http-client`	all versions	3.10.7`io.micronaut:micronaut-http-client:3.10.7`
☕Maven	`io.micronaut:micronaut-http-client`	≥ 4.0.0-M1&&< 4.10.24	4.10.24`io.micronaut:micronaut-http-client:4.10.24`
☕Maven	`io.micronaut:micronaut-http-client`	≥ 5.0.0-M1&&< 5.0.1	5.0.1`io.micronaut:micronaut-http-client:5.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.micronaut:micronaut-http-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.micronaut:micronaut-http-client to 3.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-387m-935m-c4vw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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/microna

O3 Security · Impact-Aware SCA

Is GHSA-387m-935m-c4vw in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works