dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-44503

HIGH · 7.0 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
The RedirectHandler middleware in microsoft/kiota-java (com.microsoft.kiota:microsoft-kiota-http-okHttp v1.9.0) and other Kiota libraries fails to strip sensitive HTTP headers when following 3xx redirects to a different host or scheme. Only the Authorization header is removed; Cookie, Proxy-Authorization, and all custom headers are forwarded to the redirect target.

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 · high confidence

The RedirectHandler middleware in microsoft/kiota-java (microsoft-kiota-http-okHttp v1.9.0) fails to strip sensitive HTTP headers when following 3xx redirects to a different host or scheme. Only the Authorization header is removed; Cookie, Proxy-Authorization, and custom headers are forwarded to the redirect target, potentially leaking credentials or session data to untrusted destinations.

MitigationImplement header filtering in the RedirectHandler to strip Cookie, Proxy-Authorization, and all custom headers when redirecting to a different host or scheme, similar to how Authorization is handled. Only forward safe headers (e.g., Content-Type, Accept) to redirect targets.

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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if microsoft-kiota-http-okHttp library is in use
    Inspect project dependencies (Maven pom.xml, Gradle build.gradle, or similar) for the microsoft-kiota-http-okHttp artifact
    Affected if The library is present in dependencies
  2. Check the installed version of microsoft-kiota-http-okHttp
    Locate the version declaration in your dependency management file and verify it is exactly 1.9.0 or falls within the affected range
    Affected if Version is 1.9.0 or another version known to contain the vulnerable RedirectHandler
  3. Determine if RedirectHandler is enabled in the HTTP client configuration
    Search configuration files or code that sets up the OkHttpClient for mentions of RedirectHandler or redirect handling behavior
    Affected if RedirectHandler is actively used to handle HTTP redirects
  4. Verify if the application follows redirects to different hosts or schemes
    Review application code or network configuration to confirm that 3xx redirects to cross-origin or cross-scheme destinations are possible and not blocked
    Affected if The application follows redirects to different hosts or schemes (e.g., HTTP to HTTPS, different domain)
  5. Inspect if sensitive headers are being stripped on redirects
    Examine the RedirectHandler source code or runtime behavior to confirm whether Cookie, Proxy-Authorization, and custom headers are removed when redirecting to a different host or scheme
    Affected if These headers are NOT stripped when redirecting to a different host or scheme (only Authorization is removed in vulnerable versions)

If microsoft-kiota-http-okHttp version 1.9.0 is in use with RedirectHandler enabled and the app follows cross-host/scheme redirects, sensitive headers may be leaked to untrusted destinations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement header filtering in the RedirectHandler to strip Cookie, Proxy-Authorization, and all custom headers when redirecting to a different host or scheme, similar to how Authorization is handled. Only forward safe headers (e.g., Content-Type, Accept) to redirect targets.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44503 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44503 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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