@hapi/wreck
Affected
- introduced
0, fixed18.1.1(semver)
Fixed versions
18.1.1
Fix
- Fixed version
18.1.1npm install @hapi/[email protected]
Advisory
Also known as: CVE-2026-44979
@hapi/wreck leaks sensitive Proxy-Authorization header across cross-hostname redirects
Impact
When @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped. 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.
Redirect following is opt-in. The redirects option defaults to false (no redirections followed), so applications are only affected if they have explicitly set redirects to a positive integer on the request or via Wreck.defaults({ redirects: ... }).
Patches@hapi/wreck 18.1.1 extends the cross-hostname strip set to include proxy-authorization. Upgrade to 18.1.1 or later.
Workarounds
If upgrading is not immediately possible:
false) — applications that never enable redirect following are not affected.beforeRedirect hook to manually strip proxy-authorization (and any other sensitive application headers) when redirectOptions targets a different hostname than the original request.Resources
Medium Basis: The source's own band: MODERATE
0, fixed 18.1.1 (semver)18.1.1
18.1.1npm install @hapi/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0