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-vhjm-w67q-g75c | @hapi/wreck leaks sensitive `Proxy-Authorization` header across cross-hostname redirects |
Mon, 20 Jul 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 17 Jul 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @hapi/wreck is an HTTP client utility. Prior to 18.1.1, when @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped, and the standard credential header Proxy-Authorization is forwarded intact to the redirect target, potentially exposing forward-proxy credentials to a host outside the original trust boundary when redirects are enabled through the redirects option or Wreck.defaults({ redirects: ... }). This issue is fixed in version 18.1.1. | |
| Title | @hapi/wreck : Sensitive `Proxy-Authorization` header leaked across cross-hostname redirects | |
| Weaknesses | CWE-200 CWE-522 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-20T14:35:45.343Z
Reserved: 2026-05-08T16:23:33.264Z
Link: CVE-2026-44979
Updated: 2026-07-20T14:35:41.555Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-22T01:45:15Z
Github GHSA