Which versions of @hapi/hapi are affected by GHSA-23VW-MHV5-GRV5?

@hapi/hapi (npm) versions < 18.4.1 is affected.

Is there a fix for GHSA-23VW-MHV5-GRV5?

Yes. GHSA-23VW-MHV5-GRV5 is fixed in 18.4.1, 19.1.1. Upgrade to this version or later.

Is GHSA-23VW-MHV5-GRV5 exploitable, and should I be worried?

Whether GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5?

Upgrade: @hapi/hapi to 18.4.1 or later, @hapi/hapi to 19.1.1 or later.

GHSA-23VW-MHV5-GRV5 in @hapi/hapi

Q: What is GHSA-23VW-MHV5-GRV5?

GHSA-23VW-MHV5-GRV5 is a high-severity security vulnerability in @hapi/hapi (npm), affecting versions < 18.4.1. It is fixed in 18.4.1, 19.1.1.

Q: Is there a fix for GHSA-23VW-MHV5-GRV5?

Yes. GHSA-23VW-MHV5-GRV5 is fixed in 18.4.1, 19.1.1. Upgrade to this version or later.

Q: Is GHSA-23VW-MHV5-GRV5 exploitable, and should I be worried?

Whether GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5?

Upgrade: @hapi/hapi to 18.4.1 or later, @hapi/hapi to 19.1.1 or later.

GHSA-23VW-MHV5-GRV5

GHSA-23VW-MHV5-GRV5 is a high-severity security vulnerability in @hapi/hapi (npm), affecting versions < 18.4.1. It is fixed in 18.4.1, 19.1.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Denial of Service in @hapi/hapi

Versions of @hapi/hapi prior to 18.4.1 or 19.1.1 are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.

Impact

Affected versions

@hapi/hapi (< 18.4.1) @hapi/hapi (>= 19.0.0, < 19.1.1)

Security releases

@hapi/hapi → 18.4.1 (npm) @hapi/hapi → 19.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.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade to versions 18.4.1, 19.1.1 or later.

Frequently Asked Questions

What is GHSA-23VW-MHV5-GRV5? GHSA-23VW-MHV5-GRV5 is a high-severity security vulnerability in @hapi/hapi (npm), affecting versions < 18.4.1. It is fixed in 18.4.1, 19.1.1.
Which versions of @hapi/hapi are affected by GHSA-23VW-MHV5-GRV5? @hapi/hapi (npm) versions < 18.4.1 is affected.
Is there a fix for GHSA-23VW-MHV5-GRV5? Yes. GHSA-23VW-MHV5-GRV5 is fixed in 18.4.1, 19.1.1. Upgrade to this version or later.
Is GHSA-23VW-MHV5-GRV5 exploitable, and should I be worried? Whether GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5 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 GHSA-23VW-MHV5-GRV5?
- Upgrade @hapi/hapi to 18.4.1 or later
- Upgrade @hapi/hapi to 19.1.1 or later