# CVE-2025-22227: CVE-2025-22227: Authentication Leak On Redirect With Reactor Netty HTTP Client

> Attackers can steal credentials when the Reactor Netty HTTP client follows chained redirects, requiring explicit redirect configuration.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jul 2025
- **Updated:** 23 Jun 2026
- **Also known as:** CLEANSTART-2026-CQ96086, CLEANSTART-2026-NJ85552, CLEANSTART-2026-QV47871, CLEANSTART-2026-SF24909, CLSA-2025-1763424415, CLSA-2026-1768781329, CLSA-2026-1787374807, ECHO-346e-b7b3-0c67, GHSA-4q2v-9p7v-3v22, MINI-24p8-3rh2-7fvh, MINI-2f75-3q62-gfm3, MINI-2jxf-vpv5-h4v4, MINI-55r2-9rp5-j32f, MINI-5c56-gf3r-43g7, MINI-654p-55xw-q343, MINI-6mj8-hp3x-pgcc, MINI-7hfj-hp4f-mh3q, MINI-7wc4-vmc2-3hh8, MINI-856j-xm2f-5rmm, MINI-8827-p9wr-h8cf, MINI-8jch-q9pj-8f96, MINI-8prq-99p4-hj65, MINI-8wxj-mqcp-whxm, MINI-9h6x-xjw5-74fc, MINI-fxx6-7674-g7h4, MINI-jf62-j2wv-qr55, MINI-mfcj-mg8x-4wgq, MINI-p6f7-mh23-xw6q, MINI-q4mj-3cfr-5725, MINI-qwg8-64mr-f2x9, MINI-vfv6-54pm-w7ff, MINI-wpm8-9w82-9h8h, MINI-wx25-j424-6ghx, MINI-x637-728g-2rpp, ROOT-APP-MAVEN-CVE-2025-22227

## What is CVE-2025-22227?

CVE-2025-22227 is a medium-severity vulnerability in VMware Reactor Netty, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-22227?

4 open source packages ship an affected version, including io.projectreactor.netty:reactor-netty-http.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.projectreactor.netty:reactor-netty-http` | Maven | All versions | 1.2.8 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | All versions | 1.2.8 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.3.0-M1 | 1.3.0-M5 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.3.0-M1 | 1.3.0-M5 |

## How do I fix CVE-2025-22227?

Upgrade io.projectreactor.netty:reactor-netty-http to a fixed version for your release line: 1.2.8 or 1.3.0-M5.

## Is CVE-2025-22227 being exploited?

There is no known exploitation of CVE-2025-22227 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22227 and fix it if it is affected.

What it is: CVE-2025-22227 is a medium-severity vulnerability in VMware Reactor Netty, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-22227 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.projectreactor.netty:reactor-netty-http (Maven): affected all versions; fixed in 1.2.8
- io.projectreactor.netty:reactor-netty-http (Maven): affected all versions; fixed in 1.2.8
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.3.0-M1; fixed in 1.3.0-M5
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.3.0-M1; fixed in 1.3.0-M5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22227/ (Markdown: https://insights.sbomify.com/CVE-2025-22227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22227
- OSV: https://osv.dev/vulnerability/CVE-2025-22227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22227/
Summaries are generated and may contain mistakes; the official description above is the record.