Is CVE-2026-85473 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85473 being exploited in the wild.

How severe is CVE-2026-85473?

Medium severity, with a CVSS score of 5.3, published 13 October 2026.

Is there a fix for CVE-2026-85473?

Yes: fixed in 4.6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-85473 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-85473?

Check whether you run Auth0 Java-Jwt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85473: auth0 java-jwt thread termination in timestamp claim parsing

CVE-2026-85473 · Severity: medium · CVSS 5.3 · Published 2026-10-13

The auth0 java-jwt library is a widely-used authentication library that parses JSON Web Tokens (JWTs). A malformed JWT with an out-of-range timestamp claim can cause the library to terminate a thread before validating the token's signature. An attacker can send repeated malicious JWTs to degrade or disable services that rely on this library for authentication.

Vendors: Auth0.

Quick answers

Is CVE-2026-85473 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85473 being exploited in the wild.
How severe is CVE-2026-85473?: Medium severity, with a CVSS score of 5.3, published 13 October 2026.
Which products and versions are affected?: Auth0 Java-Jwt 4.0.0 to 4.6.1.
Is there a fix for CVE-2026-85473?: Yes: fixed in 4.6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85473 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-85473?: Check whether you run Auth0 Java-Jwt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.6.2

Technical details

The vulnerability is an improper input validation issue in JWT timestamp claim parsing (exp, nbf, iat fields). The out-of-range condition triggers an unhandled exception that terminates the parsing thread prior to signature verification, requiring no authentication or user interaction. An attacker can exploit this via network requests containing crafted JWTs to cause a denial-of-service condition through thread exhaustion or repeated thread termination.

Affected products

auth0 java-jwt 4.0.0 to 4.6.1

Timeline

2026-10-13: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.