How severe is CVE-2015-9236?

No CVSS score has been assigned to CVE-2015-9236 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-9236?

CVE-2015-9236 affects the following packages: hapi (npm). Ecosystems affected: npm.

How do I fix CVE-2015-9236?

Update hapi to 11.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9236 is resolved across your whole dependency graph.

How do I detect CVE-2015-9236 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-9236 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2015-9236 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-9236 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-9236?

CVE-2015-9236 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-9236?

CVE-2015-9236 is classified as CWE-284 (CWE-284), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-9236 published, and has it been updated?

CVE-2015-9236 was published on June 7, 2018 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2015-9236 — hapi

CVE-2015-9236 is a CWE-284 vulnerability in hapi. A fix is available for hapi — see the affected versions and patch details below.

Incorrect handling of CORS preflight request headers in hapi

Published

Jun 7, 2018

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk-0.02%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hapinpm

57Kdownloads / week

Description

Versions of hapi prior to 11.0.0 implement CORS incorrectly, allowing for configurations that at best return inconsistent headers, and at worst allow cross-origin activities that are expected to be forbidden.

If the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.

Recommendation

Update to version 11.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hapi`	all versions	11.0.0`npm install hapi@11.0.0`

Affected Products

1 product · 1 configurations

Application

hapihapijs

< 11.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hapi to 11.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9236 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Versions of `hapi` prior to 11.0.0 implement CORS incorrectly, allowing for configurations that at best return inconsistent headers, and at worst allow cross-origin activities that are expected to be forbidden. If the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route. ## Recommendation Update to version 11.0.0 or later.

O3 Security · Impact-Aware SCA

Is CVE-2015-9236 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works