CVE-2026-44979: @hapi/wreck @hapi/wreck Leaks Sensitive `Proxy-Authorization` Header Vulnerability

MODERATE
Advisory Identifier: GHSA-vhjm-w67q-g75c
Share
CWE-522 CWE-200
Published
Advisory Summary

CVE-2026-44979 is a MODERATE @hapi/wreck leaks sensitive `proxy-authorization` header vulnerability (CWE-522: Insufficiently Protected Credentials) affecting @hapi/wreck libraries in the npm ecosystem. The issue involves @hapi/wreck leaks sensitive `proxy-authorization` header across cross-hostname redirects. Remediation is available by upgrading affected packages to version 18.1.1.

CVE-2026-44979 at a Glance

CVE Identifier CVE-2026-44979
GHSA Identifier GHSA-vhjm-w67q-g75c
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product @hapi/wreck
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-44979

To remediate this vulnerability, upgrade all affected @hapi/wreck dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@hapi/wreck fixed: 18.1.1 
npm install @hapi/wreck@18.1.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @hapi/wreck

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-44979, inspect your project dependencies using npm:

npm ls @hapi/wreck

Analyze the terminal output to locate any version of @hapi/wreck in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 18.1.1), your application is affected.

Note: The npm ls @hapi/wreck command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In @hapi/wreck, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 - Related: [CVE-2024-30260 / GHSA-3787-6prv-h9w3 ](https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3)(undici) - [RFC 7235 §4.4 — Proxy-Authorization](https://datatracker.ietf.org/doc/html/rfc7235#section-4.4)

CVE-2026-44979 Affected @hapi/wreck Versions

1 component(s)
Fixed Versions:
18.1.1
Product / Package Ecosystem Affected Versions Fixed Version
@hapi/wreck
npm/@hapi/wreck
npm
< 18.1.1
18.1.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/hapijs/wreck/security/advisories/GHSA-vhjm-w67q-g75c
GitHub Advisory / Wiki ADVISORY
https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3
Security Fix Commit FIX COMMIT
https://github.com/hapijs/wreck/commit/a5b6fac9c684621c1d5733d10a0257697cfea373
@hapi/wreck Source Repository REPOSITORY
https://github.com/hapijs/wreck

Frequently Asked Questions

What is CVE-2026-44979?
CVE-2026-44979 is a security vulnerability in @hapi/wreck involving @hapi/wreck leaks sensitive `Proxy-Authorization` header across cross-hostname redirects under CWE-522: Insufficiently Protected Credentials.
Which @hapi/wreck versions are affected?
Affected versions include releases prior to 18.1.1 across affected packages: @hapi/wreck.
What version fixes CVE-2026-44979?
Upgrading to 18.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @hapi/wreck affected?
Yes, @hapi/wreck is affected in releases prior to 18.1.1. Upgrade your dependency to 18.1.1 or later.
What CWE is associated with CVE-2026-44979?
CVE-2026-44979 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check npm dependencies for CVE-2026-44979?
Run the dependency tree command: 'npm ls @hapi/wreck'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vhjm-w67q-g75c",
  "modified" : "2026-05-27T00:38:09Z",
  "published" : "2026-05-27T00:38:09Z",
  "aliases" : [ "CVE-2026-44979" ],
  "summary" : "@hapi/wreck leaks sensitive `Proxy-Authorization` header across cross-hostname redirects",
  "details" : "### Impact\nWhen `@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.\n\nRedirect 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: ... })`.\n\n### Patches\n`@hapi/wreck` 18.1.1 extends the cross-hostname strip set to include `proxy-authorization`. Upgrade to 18.1.1 or later.\n\n### Workarounds\nIf upgrading is not immediately possible:\n- Leave redirects at its default (`false`) — applications that never enable redirect following are not affected.\n- If redirects are required, set redirects: 0 when calling endpoints with sensitive headers, or strip Proxy-Authorization from the headers before issuing the request.\n- 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.\n\n### Resources\n- Related: [CVE-2024-30260 / GHSA-3787-6prv-h9w3 ](https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3)(undici)\n- [RFC 7235 §4.4 — Proxy-Authorization](https://datatracker.ietf.org/doc/html/rfc7235#section-4.4)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@hapi/wreck"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "18.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/hapijs/wreck/security/advisories/GHSA-vhjm-w67q-g75c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hapijs/wreck/commit/a5b6fac9c684621c1d5733d10a0257697cfea373"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/hapijs/wreck"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-522" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-27T00:38:09Z",
    "nvd_published_at" : null
  }
}