CVE-2026-44979

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@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 v3
6.3
EG Score
6.3(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
17.7%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github, github_pr.
github_commit

commit a5b6fac9c684 (hapijs/wreck)

Fix landed in hapijs/wreck commit a5b6fac9c684 — awaiting tagged release

https://github.com/hapijs/wreck/commit/a5b6fac9c684621c1d5733d10a0257697cfea373
github_pr

fix: strip proxy-authorization header on redirect

Fix merged in hapijs/wreck PR #312 on 2026-05-06 — awaiting tagged release

https://github.com/hapijs/wreck/pull/312
github Patch Available

Sensitive `Proxy-Authorization` header leaked across cross-hostname redirects · Advisory · hapijs/wreck · GitHub

https://github.com/hapijs/wreck/security/advisories/GHSA-vhjm-w67q-g75c

Vendor Advisories for CVE-2026-44979(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@hapi/wreck—18.1.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:15 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-17 21:19 UTCEG score recompute▲ 6.30
  8. 2026-07-17 21:19 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-05-27 01:14 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44979?
CVE-2026-44979 is a medium vulnerability published on May 27, 2026. @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…
When was CVE-2026-44979 disclosed?
CVE-2026-44979 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44979 actively exploited?
CVE-2026-44979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44979?
CVE-2026-44979 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-44979?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44979, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44979

Explore →

Is Your Infrastructure Affected by CVE-2026-44979?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs