Advisory

GHSA-vhjm-w67q-g75c

Also known as: CVE-2026-44979

Summary

@hapi/wreck leaks sensitive Proxy-Authorization header across cross-hostname redirects

Details

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:

  • Leave redirects at its default (false) — applications that never enable redirect following are not affected.
  • If redirects are required, set redirects: 0 when calling endpoints with sensitive headers, or strip Proxy-Authorization from the headers before issuing the request.
  • Use the beforeRedirect hook to manually strip proxy-authorization (and any other sensitive application headers) when redirectOptions targets a different hostname than the original request.

Resources

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-27 00:38 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

@hapi/wreck

npm · All systems

Affected

  • introduced 0, fixed 18.1.1 (semver)

Fixed versions

18.1.1

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences