Is @hapi/wreck safe to use?

Vulert records 2 vulnerabilities for @hapi/wreck in npm: 0 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @hapi/wreck's Vulert package health score?

Vulert scores @hapi/wreck 72/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @hapi/wreck affected?

No. 18.1.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @hapi/wreck should I use?

18.1.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @hapi/wreck have?

2 vulnerabilities are recorded for @hapi/wreck in the npm ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @hapi/wreck vulnerabilities disclosed?

2 vulnerabilities were recorded for @hapi/wreck in the last 12 months, and the oldest entry in this database dates to 27 May 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @hapi/wreck are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @hapi/wreck for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the @hapi/wreck version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · npm · Package report

@hapi/wreck: vulnerability history, versions and safety

@hapi/wreck is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 14 releases, from May 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded M2

0 with no fix published

Every vulnerability has a patched version to move to.

2 in the last 12 months

Most recent disclosure 11 Jun 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @hapi/wreck vulnerabilities

Vulert verdict on @hapi/wreck 18.1.2 i

Updated on 23 Oct 2026

Good news: 18.1.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Quiet

What to do: Stay on 18.1.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 18.1.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 18.1.2 — unaffected i
Vulnerabilities on record 2 over 1 year · 2 in the last year i
Latest disclosure 11 Jun 2026 i
Highest CVSS 6.5 i
With no published fix 0 i
Depended on by 975 packages i
Stars 375 i
OpenSSF scorecard 3/10 i
Last release 5 months ago i
Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for @hapi/wreck, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
18.1.2	20 May 2026	none	BSD-3-Clause	—	Details →
18.1.1	06 May 2026	M1	BSD-3-Clause	Yes	Details →
18.1.0	10 Apr 2024	M2	BSD-3-Clause	Yes	Details →
18.0.2	10 Apr 2024	M2	BSD-3-Clause	Yes	Details →
18.0.1	11 Feb 2023	M2	BSD-3-Clause	Yes	Details →
18.0.0	07 May 2022	M2	BSD-3-Clause	Yes	Details →
17.2.0	25 Mar 2022	M2	BSD-3-Clause	Yes	Details →
17.1.0	23 Nov 2020	M2	BSD-3-Clause	Yes	Details →
17.0.0	04 Jan 2020	M2	BSD-3-Clause	Yes	Details →
16.0.1	15 Oct 2019	M2	BSD-3-Clause	Yes	Details →
16.0.0	15 Oct 2019	M2	BSD-3-Clause	Yes	Details →
15.1.0	18 Sep 2019	M2	BSD-3-Clause	Yes	Details →
15.0.2	15 Aug 2019	M2	BSD-3-Clause	Yes	Details →
15.0.1	16 Apr 2019	M2	BSD-3-Clause	Yes	Details →
15.0.0	30 Mar 2019	M2	BSD-3-Clause	Yes	Details →

All 15 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for @hapi/wreck

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2026-48022: @hapi/wreck Sensitive Credential Headers Leak Across Cross-Port and Cross-Scheme Redirects	6.5 medium	18.1.2	11 Jun 2026
CVE-2026-44979: @hapi/wreck Exposes Proxy-Authorization Header During Cross-Hostname Redirects	6.3 medium	18.1.1	27 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315