CVE-2026-44979: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in hapijs wreck
@hapi/wreck is an HTTP client utility. Prior to 18.1.1, when @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped, and 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 when redirects are enabled through the redirects option or Wreck.defaults({ redirects: ... }). This issue is fixed in version 18.1.1.
AI Analysis
Technical Summary
@hapi/wreck versions before 18.1.1 do not strip the Proxy-Authorization header when following HTTP 3xx redirects to a different hostname. While Authorization and Cookie headers are removed, Proxy-Authorization headers are forwarded intact, potentially exposing sensitive forward-proxy credentials to untrusted hosts. This behavior occurs when redirects are enabled via the redirects option or Wreck.defaults({ redirects: ... }). The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). The issue is resolved in version 18.1.1.
Potential Impact
Forward-proxy credentials contained in the Proxy-Authorization header may be exposed to external hosts during HTTP redirects, potentially allowing unauthorized actors to obtain sensitive authentication information. This exposure can compromise proxy authentication security boundaries.
Mitigation Recommendations
Upgrade @hapi/wreck to version 18.1.1 or later, where the Proxy-Authorization header is properly stripped on redirects to different hostnames. No other mitigation is indicated. Patch status is confirmed fixed in 18.1.1.
CVE-2026-44979: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in hapijs wreck
Description
@hapi/wreck is an HTTP client utility. Prior to 18.1.1, when @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped, and 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 when redirects are enabled through the redirects option or Wreck.defaults({ redirects: ... }). This issue is fixed in version 18.1.1.
CVSS v4.0
Score 6.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@hapi/wreck versions before 18.1.1 do not strip the Proxy-Authorization header when following HTTP 3xx redirects to a different hostname. While Authorization and Cookie headers are removed, Proxy-Authorization headers are forwarded intact, potentially exposing sensitive forward-proxy credentials to untrusted hosts. This behavior occurs when redirects are enabled via the redirects option or Wreck.defaults({ redirects: ... }). The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). The issue is resolved in version 18.1.1.
Potential Impact
Forward-proxy credentials contained in the Proxy-Authorization header may be exposed to external hosts during HTTP redirects, potentially allowing unauthorized actors to obtain sensitive authentication information. This exposure can compromise proxy authentication security boundaries.
Mitigation Recommendations
Upgrade @hapi/wreck to version 18.1.1 or later, where the Proxy-Authorization header is properly stripped on redirects to different hostnames. No other mitigation is indicated. Patch status is confirmed fixed in 18.1.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T16:23:33.264Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b401a34329bf928c718b2
Added to database: 07/18/2026, 08:58:02 UTC
Last enriched: 07/25/2026, 22:51:02 UTC
Last updated: 08/31/2026, 10:52:09 UTC
Views: 62
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.