Summary
Unsafe Merging of CORS Configuration Conflict in hapi
Versions of hapi prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.
Impact
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
Update hapi to version 11.1.4 or later.
Frequently Asked Questions
- What is CVE-2015-9243? CVE-2015-9243 is a medium-severity security vulnerability in hapi (npm), affecting versions < 11.1.4. It is fixed in 11.1.4.
- Which versions of hapi are affected by CVE-2015-9243? hapi (npm) versions < 11.1.4 is affected.
- Is there a fix for CVE-2015-9243? Yes. CVE-2015-9243 is fixed in 11.1.4. Upgrade to this version or later.
- Is CVE-2015-9243 exploitable, and should I be worried? Whether CVE-2015-9243 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 CVE-2015-9243 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 CVE-2015-9243? Upgrade
hapito 11.1.4 or later.