Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hq3h-g68c-hp78 | urllib's cross-origin redirects preserve credential-bearing request headers, leading to potential credential leakage |
Tue, 25 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | urllib is an HTTP client for Node.js that supports authentication, redirects, timeouts, and other request features. Prior to 4.9.1 and 2.44.1, urllib follows redirects through followRedirect but reuses caller-supplied options across origins. In src/HttpClient.ts, #requestInternal recursively calls this.#requestInternal(nextUrl.href, options, requestContext), causing options.headers and auth or digestAuth values to be reused when the redirect target has a different scheme, host, or port. Authorization, Cookie, Proxy-Authorization, x-api-key, x-auth-token, and x-access-token can therefore be sent to an attacker-controlled redirected origin, exposing credentials intended for the original origin and potentially allowing reuse against the original partner API or related services. No user interaction is required. This issue is fixed in versions 2.44.1 and 4.9.1. | |
| Title | urllib: Cross-origin redirects preserve credential-bearing request headers, leading to potential credential leakage | |
| Weaknesses | CWE-200 CWE-201 CWE-522 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-25T18:25:40.662Z
Reserved: 2026-06-16T23:11:20.213Z
Link: CVE-2026-55553
No data.
Status : Received
Published: 2026-08-25T17:17:32.113
Modified: 2026-08-25T17:17:32.113
Link: CVE-2026-55553
No data.
OpenCVE Enrichment
Updated: 2026-08-25T18:30:04Z
Github GHSA