External risk intelligence

MicroProfile JWT Clock Skew Allows Expired Token Authentication

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-111243

This vulnerability affects MicroProfile JWT validation, a common component in web applications and APIs used to handle authentication. Because these services are frequently deployed as internet-facing endpoints to manage user access and session validation, they are commonly exposed to the public internet.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in MicroProfile JWT that could allow an attacker to use an expired token for authentication, bypassing expiration and time-based security checks. This affects the security of applications relying on MicroProfile JWT for access control. The primary concern is to determine if our systems utilize this specific technology.

  • Expired tokens may still grant access.
  • Confirms relevance and exposure of MicroProfile JWT.
  • Understand technology's authentication validation.

Attack Path

How an attacker could exploit the issue

An attacker could leverage a misconfigured MicroProfile JWT setting to bypass time-based token validations, allowing them to use expired authentication tokens. This occurs because a negative clock skew setting prevents the system from checking token expiration and other time-sensitive details. If successful, an attacker could gain unauthorized access to the system.

  • An attacker needs network access.
  • The attacker triggers the vulnerability by providing an expired token.
  • Risk includes unauthorized access and data compromise.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory's configuration, this vulnerability could allow an attacker in possession of an expired token to authenticate and gain unauthorized access. This occurs because a negative MicroProfile JWT clock skew setting disables the validation of token expiration and other time-based claims.

  • Expired tokens could be reused.
  • An attacker could exploit this.
  • Unauthorized access may result.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts MicroProfile JWT validation, suggesting that platform or application teams responsible for identity and access management services are likely involved. The first practical step is to identify all instances of the affected technology, confirm their exposure and criticality, and then coordinate with the accountable owner to plan remediation.

  • Identify and confirm affected systems.
  • Determine business criticality and exposure.
  • Plan remediation with accountable owner.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MicroProfile JWT?

MicroProfile JWT is a specification used by Java-based web applications to handle identity and authentication. It allows services to verify JSON Web Tokens (JWT) to determine who a user is and what they are allowed to do. Developers use it to build secure, interoperable authentication systems for APIs and microservices.

How does CVE-2026-111243 break authentication?

This flaw belongs to the CWE-613 weakness class, which deals with insufficient session expiration. In this case, the software fails to reject a negative clock skew setting. This misconfiguration causes the system to stop checking if a token has expired, effectively allowing an old, invalid token to be treated as legitimate.

Do I need to do anything if my clock skew is positive?

No. The vulnerability is specifically triggered by a negative clock skew configuration. If your system uses a positive or zero value for clock skew, the mechanism responsible for enforcing token expiration remains active and continues to validate the token's time-based claims correctly.

Is my system at risk if it faces the internet?

According to Halo Surface Signal, this vulnerability is highly relevant for systems exposed to the public internet. Because MicroProfile JWT components often manage user sessions at the network edge, an internet-facing configuration provides an easier path for an attacker to present an expired token and attempt unauthorized access.

How should I respond to this vulnerability?

Begin by auditing your applications to locate services using MicroProfile JWT and checking their current clock skew configuration. If you identify a negative setting, verify your version against the advisory. Coordinate with your application security team to plan an upgrade to version 10.3.0 or 11.0.0-M2, which address this flaw.

References