CVE-2026-41715
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 specific scenarios involving HTTP redirects from a secure to an insecure endpoint, the Reactor Netty HTTP client may leak credentials. In order for this to happen, the HTTP client must have been explicitly configured to follow redirects. Affected versions: Reactor Netty 1.0.0 through 1.0.51; 1.1.0 through 1.1.35; 1.2.0 through 1.2.17; 1.3.0 through 1.3.5.
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 (authentication headers, cookies, or other sensitive data) are inadvertently transmitted to insecure endpoints when following redirects from HTTPS to HTTP. This occurs specifically when the client is configured to automatically follow redirects, causing sensitive authentication data to be sent over unencrypted connections.
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 versionInspect your project's dependency management file (pom.xml, build.gradle, or similar) for the reactor-netty dependency version, or run 'jar -tf reactor-netty-*.jar | grep "Implementation-Version"' if the JAR is availableAffected if The version is 1.0.51 or lower, 1.1.35 or lower, 1.2.17 or lower, or 1.3.5 or lower
-
Verify HTTP client redirect configurationSearch your codebase for HttpClient redirect configuration - look for .followRedirect(true) or similar fluent API calls, or check for 'reactor.netty.http.followRedirect' property in configuration filesAffected if Automatic redirect following is enabled (followRedirect set to true or not explicitly disabled)
-
Confirm authentication credential usageSearch for WebSocket or HTTP client setups that include credentials - look for .basicAuth(), .headers(HttpHeaders::setAuthorization), or credential-bearing URL patterns in your HTTP client initialization codeAffected if The HTTP client is configured to send authentication credentials (basic auth, bearer token, or other credential-based authentication)
-
Check for mixed HTTPS-to-HTTP redirect scenariosReview your application's HTTP client usage patterns - trace network calls or review redirect endpoint configurations to see if redirects from HTTPS endpoints to HTTP endpoints could occurAffected if The client may redirect from an authenticated HTTPS endpoint to an HTTP endpoint
You are affected if you use Reactor Netty at or below the patched versions AND your HTTP client follows redirects automatically while transmitting authentication credentials to endpoints that could redirect to insecure HTTP URLs.
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.
dbcve · scopedUpgrade to a patched version of Reactor Netty (not yet specified in available advisories), or temporarily disable automatic redirect following in the HTTP client configuration until patching is possible.
Reactor Netty 1.0.52+ / 1.1.36+ / 1.2.18+ / 1.3.6+ (upgrade to the latest 1.3.x stable release for the most current security fixes)
- 1. Identify the current Reactor Netty version in use by examining project dependencies (e.g., in pom.xml, build.gradle, or gradle.lock file
- 2. For Reactor Netty 1.0.x: upgrade to version 1.0.52 or later
- 3. For Reactor Netty 1.1.x: upgrade to version 1.1.36 or later
- 4. For Reactor Netty 1.2.x: upgrade to version 1.2.18 or later
- 5. For Reactor Netty 1.3.x: upgrade to version 1.3.6 or later
- 6. Update the dependency version in your build configuration file
- 7. Rebuild and test the application to ensure the upgrade does not break existing functionality
- 8. Verify that HTTP redirect handling now properly protects credentials when redirects occur from HTTPS to HTTP endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41715 — 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-2026-41715 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