CVE-2016-10525: When attempting to allow authentication mode `try` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue w

Q: How do I fix CVE-2016-10525?

hapi-auth-jwt2: upgrade to newer than 5.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2016-10525 being exploited?

CVE-2016-10525 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10525 affect?

CVE-2016-10525 affects hapi-auth-jwt2. Severity is critical (CVSS 9.8). When attempting to allow authentication mode `try` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue whereby people could bypass authentication.

Q: How urgent is CVE-2016-10525?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2016-10525 is a critical-severity flaw (CVSS 9.8) affecting hapi-auth-jwt2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Weakness	CWE-287
Published	2018-05-29
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: dwyl

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-05-29 20:29 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

dwyl hapi-auth-jwt2 UPGRADE

Affected: <= 5.1.1

Fixed in: newer than 5.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy hapi-auth-jwt2 || rpm -q hapi-auth-jwt2 || hapi-auth-jwt2 --version

2. UPGRADE to newer than 5.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade hapi-auth-jwt2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade hapi-auth-jwt2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10525?

hapi-auth-jwt2: upgrade to newer than 5.1.1. Exact commands for each OS are on this page.

Is CVE-2016-10525 being exploited?

CVE-2016-10525 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10525 affect?

CVE-2016-10525 affects hapi-auth-jwt2. Severity is critical (CVSS 9.8). When attempting to allow authentication mode `try` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue whereby people could bypass authentication.

How urgent is CVE-2016-10525?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs