CVE-2016-10525

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.47%
Third-Party Advisory github.com Third-Party Advisory github.com Third-Party Advisory nodesecurity.io
Affected: HackerOne hapi-auth-jwt2 node module
Published at:
Updated at:

References

Link Tags
https://nodesecurity.io/advisories/81 third party advisory
https://github.com/dwyl/hapi-auth-jwt2/pull/112 third party advisory
https://github.com/dwyl/hapi-auth-jwt2/issues/111 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2016-10525?
CVE-2016-10525 has been scored as a critical severity vulnerability.
How to fix CVE-2016-10525?
To fix CVE-2016-10525, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-10525 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-10525 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2016-10525?
CVE-2016-10525 affects HackerOne hapi-auth-jwt2 node module.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.