# CVE-2026-44979: hapi wreck sensitive information leak in Proxy-Authorization header

Source: https://junglewise.ai/threats/cve-2026-44979-hapi-wreck-sensitive-information-leak-in-proxy-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-17. Updated: 2026-07-17  
License: CC BY 4.0 with a link back

CVE-2026-44979 · Severity: medium · CVSS 4 · Published 2026-07-17

@hapi/wreck is a software tool used by developers to make web requests. A security issue was found where the tool fails to remove sensitive proxy login information when it is automatically redirected from one website to another. This could allow an untrusted third-party website to steal credentials used to access your organization's internal network or proxy services.

Vendors: [Hapi](https://junglewise.ai/threats/vendors/hapi), [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-44979 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44979 being exploited in the wild.

**How severe is CVE-2026-44979?** Medium severity, with a CVSS score of 4, published 17 July 2026.

**Which products and versions are affected?** Hapi Wreck < 18.1.1; @hapi/wreck (npm) < 18.1.1, SEMVER:introduced=0,fixed=18.1.1.

**Is there a fix for CVE-2026-44979?** Yes. @hapi/wreck (npm): upgrade to 18.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-44979 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-44979?** Check whether you run Hapi Wreck or @hapi/wreck (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @hapi/wreck (npm): upgrade to 18.1.1 or later

  ```sh
  npm install @hapi/wreck@18.1.1
  ```


## Technical details

An information disclosure vulnerability exists in @hapi/wreck prior to version 18.1.1. When the library is configured to follow HTTP redirects (via the 'redirects' option), it correctly strips 'Authorization' and 'Cookie' headers when moving to a different hostname, but fails to strip the 'Proxy-Authorization' header. This allows the sensitive proxy credential header to be forwarded to the redirect target. An attacker who controls a URL that a vulnerable application requests can trigger a 3xx redirect to a server they control to capture these credentials. The vulnerability is patched in version 18.1.1.

## Affected products

- hapi wreck < 18.1.1

## Identifiers

- CVE-2026-44979
- GHSA-vhjm-w67q-g75c

## Timeline

- 2026-05-04: other: Initial fix committed to repository
- 2026-05-06: patched: Version 18.1.1 released
- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-07-17: disclosed: CVE published to NVD

## References

- [https://github.com/hapijs/wreck/commit/a5b6fac9c684621c1d5733d10a0257697cfea373](https://github.com/hapijs/wreck/commit/a5b6fac9c684621c1d5733d10a0257697cfea373)
- [https://github.com/hapijs/wreck/pull/312](https://github.com/hapijs/wreck/pull/312)
- [https://github.com/hapijs/wreck/releases/tag/v18.1.1](https://github.com/hapijs/wreck/releases/tag/v18.1.1)
- [https://github.com/hapijs/wreck/security/advisories/GHSA-vhjm-w67q-g75c](https://github.com/hapijs/wreck/security/advisories/GHSA-vhjm-w67q-g75c)

## Related threats

- [hapijs @hapi/wreck credential leak in cross-origin redirects](https://junglewise.ai/threats/cve-2026-48022-hapijs-hapi-wreck-credential-leak-in-cross-origin-redirects)