CVE-2015-9236

Hapi versions less than 11.0.0 implement CORS incorrectly and allowed for configurations that at best returned inconsistent headers and at worst allowed cross-origin activities that were 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.

Published: 2018-05-31 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-9236 is rated Moderate Risk (47.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.54%). EPSS rose +1.29% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2015-9236

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.25% 1.54% +1.29%
2 2025-05-01 0.26% 0.25% -0.01%
3 2025-03-17 — 0.26% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-9236

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2015-9236

GitHub Security Advisory for CVE-2015-9236

GHSA-vwrf-r5r4-7775 · Severity: medium · Ecosystem: npm — Incorrect handling of CORS preflight request headers in hapi

Affected software / configurations for CVE-2015-9236

Vendor Product Version Raw CPE
hapijs hapi < 11.0.0 cpe:2.3:a:hapijs:hapi:*:*:*:*:*:node.js:*:*

References for CVE-2015-9236

URL Tags
https://github.com/hapijs/hapi/issues/2840 Patch Third Party Advisory
https://github.com/hapijs/hapi/issues/2850 Release Notes Third Party Advisory
https://nodesecurity.io/advisories/45 Third Party Advisory
cvelogic Threat Intelligence