What is CVE-2026-44979?

CVE-2026-44979 is a medium-severity security vulnerability in @hapi/wreck (npm), affecting versions < 18.1.1. It is fixed in 18.1.1.

Which versions of @hapi/wreck are affected by CVE-2026-44979?

@hapi/wreck (npm) versions < 18.1.1 is affected.

Is there a fix for CVE-2026-44979?

Yes. CVE-2026-44979 is fixed in 18.1.1. Upgrade to this version or later.

Is CVE-2026-44979 exploitable, and should I be worried?

Whether CVE-2026-44979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-44979 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-44979?

Upgrade @hapi/wreck to 18.1.1 or later.

CVE-2026-44979 in @hapi/wreck | Intelligent Application Security

Q: Which versions of @hapi/wreck are affected by CVE-2026-44979?

@hapi/wreck (npm) versions < 18.1.1 is affected.

Q: Is there a fix for CVE-2026-44979?

Yes. CVE-2026-44979 is fixed in 18.1.1. Upgrade to this version or later.

Q: Is CVE-2026-44979 exploitable, and should I be worried?

Whether CVE-2026-44979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-44979 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-44979?

Upgrade @hapi/wreck to 18.1.1 or later.

Summary

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 (undici)
RFC 7235 §4.4, Proxy-Authorization

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: ... }).

Affected versions

@hapi/wreck (< 18.1.1)

Security releases

@hapi/wreck → 18.1.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

@hapi/wreck 18.1.1 extends the cross-hostname strip set to include proxy-authorization. Upgrade to 18.1.1 or later.

Frequently Asked Questions

What is CVE-2026-44979? CVE-2026-44979 is a medium-severity security vulnerability in @hapi/wreck (npm), affecting versions < 18.1.1. It is fixed in 18.1.1.
Which versions of @hapi/wreck are affected by CVE-2026-44979? @hapi/wreck (npm) versions < 18.1.1 is affected.
Is there a fix for CVE-2026-44979? Yes. CVE-2026-44979 is fixed in 18.1.1. Upgrade to this version or later.
Is CVE-2026-44979 exploitable, and should I be worried? Whether CVE-2026-44979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-44979 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-44979? Upgrade @hapi/wreck to 18.1.1 or later.

Other vulnerabilities in @hapi/wreck

CVE-2026-44979