npm package report

Is @hapi/wreck safe?

2 known vulnerabilities, worst severity MODERATE.

cvss
6.5

how bad it is if exploited, out of 10

epss
0.20%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-x426-x7cc-3fpc, the advisory selected below

// advisories

GHSA-x426-x7cc-3fpc

MODERATECVE-2026-48022

Wreck strips credential headers (Authorization, Cookie, Proxy-Authorization) before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port. As a result, credentials are forwarded intact across same-host port changes and HTTPS-to-HTTP downgrades, allowing a co-tenant on an adjacent port or a network-position attacker capable of forging a redirect

Affected
>=0, <18.1.2, < 18.1.2
Fixed in
18.1.2
Weakness
CWE-200
Published
2026-06-11
Source
osv

NVDMITREOSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:50 UTC. The most recent advisory here was published 2026-06-11. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @hapi/wreck safe? npm package security report | CyberXYZ