CVE-2025-22227
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Reactor Netty HTTP client has a vulnerability where credentials are leaked during chained redirect scenarios when the client is explicitly configured to follow redirects. The credential leakage occurs due to improper handling of authentication headers or credentials across multiple redirect hops.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Reactor Netty dependency usageReview project dependencies (Maven pom.xml, Gradle build.gradle, or runtime classpath) for reactor-netty, reactor-netty-http, or reactor-netty-core artifactsAffected if Reactor Netty HTTP client library is present in the application
-
Determine installed Reactor Netty versionCheck the exact version of reactor-netty-core or reactor-netty-http in your dependency management files or resolved libraries. Compare your version against the affected version range for this CVEAffected if Running an unpatched version of Reactor Netty within the affected version range
-
Verify HTTP client redirect configurationSearch codebase for HttpClient configuration calls - look for .followRedirect(true), .redirect() method calls, or any custom redirect handling logic that enables automatic redirectsAffected if The HTTP client is explicitly configured to automatically follow redirects
-
Identify credential or auth header usage in HTTP requestsAudit HTTP client code for credential handling - search for .basicAuth(), .headers(h -> h.setBasicAuth()), Bearer token placement, or any authorization header construction being used with redirect-following clientsAffected if Credentials, Basic Auth, Bearer tokens, or custom authorization headers are being sent through the HTTP client
User is affected if using an unpatched version of Reactor Netty with an HTTP client that has redirect-following enabled AND is transmitting credentials or authentication headers through that client.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Reactor Netty to the patched version once available, and review any HTTP client configurations that use redirect following to ensure no credentials are exposed in redirect chains.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22227 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data