CVE-2025-22227: Authentication Leak On Redirect With Reactor Netty HTTP Client
In some specific scenarios with chained redirects, Reactor Netty HTTP client leaks credentials. In order for this to happen, the HTTP client must have been explicitly configured to follow redirects.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/io.projectreactor.netty:reactor-netty-httpto a version that resolves this vulnerability.Fixed in 1.2.8 - Upgrade
Upgrade
maven/io.projectreactor.netty:reactor-netty-httpto a version that resolves this vulnerability.Fixed in 1.3.0-M5 - Configuration
Disable automatic following of redirects in the Reactor Netty HTTP client configuration (do not enable follow redirects) unless strictly required.
Reactor Netty HTTP client follow redirects = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22227?
CVE-2025-22227 is considered a medium severity vulnerability due to the potential for credential leakage.
How do I fix CVE-2025-22227?
To fix CVE-2025-22227, avoid configuring the Reactor Netty HTTP client to follow redirects or implement adequate security measures for credential handling.
What versions of Reactor Netty are affected by CVE-2025-22227?
CVE-2025-22227 affects all versions of Reactor Netty configured to follow redirects.
What is the impact of CVE-2025-22227 on security?
The impact of CVE-2025-22227 is that it may expose sensitive credentials to unintended recipients during chained redirects.
How can I confirm if my application is vulnerable to CVE-2025-22227?
You can confirm vulnerability to CVE-2025-22227 by checking if your application’s Reactor Netty HTTP client is configured to follow redirects.