External risk intelligence

MicroProfile JWT Role Enforcement Bypass Affects JAX-RS Resources

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-111244

The vulnerability affects JAX-RS resources protected by MicroProfile JWT. These resources are commonly used to build web applications and APIs that are exposed to the internet. Because these components are frequently deployed as public-facing services for authentication and access control, the vulnerable surface is commonly reachable in standard real-world web deployments.

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 has been identified in how MicroProfile JWT handles access control for JAX-RS resources, potentially allowing unauthorized access to sensitive information or functionalities. This issue arises from how access constraints are enforced, particularly when roles are not explicitly defined or when constraints are inherited. The primary concern is to confirm if our environment utilizes these specific configurations and is therefore exposed.

  • Access rules for some web application features are not enforced.
  • Critical for confirming if our systems are at risk.
  • Assess relevance and exposure to our digital assets.

Attack Path

How an attacker could exploit the issue

A remote attacker can bypass access controls in JAX-RS resources that are protected by MicroProfile JWT, potentially accessing sensitive information or functionality. This occurs because certain role-based access constraints are not enforced as expected, allowing unauthorized users, even unauthenticated ones in some cases, to invoke resources.

  • Requires network access.
  • Triggers by invoking restricted resources.
  • Risk: unauthorized access and data compromise.

Live Threat

Current exploitation, exposure, and threat context

When MicroProfile JWT role-based access control is used, JAX-RS resources with specific access constraints may be improperly enforced. This could allow unauthorized callers to access resources that should be restricted, potentially even without authentication in some configurations.

  • Restricted JAX-RS resources could be exposed.
  • Unauthenticated or unauthorized callers may access resources.
  • Unauthorized access to sensitive application functions.

Operational Fix

Recommended remediation, mitigation, and detection steps

The secure implementation of JAX-RS resources using MicroProfile JWT role-based access control is affected by this vulnerability, suggesting that application owners and platform teams responsible for API security should prioritize addressing it. The initial step involves identifying all instances of the affected technology, confirming their network reachability and business criticality, and then assigning ownership for remediation planning based on assessed risk.

  • Application owners should lead remediation efforts.
  • Verify reachability and business criticality of affected resources.
  • Plan maintenance windows for applying updates.

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 and how is it used?

MicroProfile JWT is a specification that enables role-based access control for Java-based web services. Developers use it to secure APIs by validating JSON Web Tokens (JWT) to ensure that only authorized users can access specific functions within JAX-RS web resources.

Why does CVE-2026-111244 cause an access control failure?

This vulnerability, classified as CWE-863 (Incorrect Authorization), means the system fails to correctly verify a user's permissions. Because the logic errors cause the software to ignore or misinterpret declared access rules, it grants entry to restricted resources even when they should be protected or blocked.

How does an attacker trigger this vulnerability?

An attacker triggers this by sending network requests to specific JAX-RS endpoints that rely on affected role-based configurations. Simply browsing or calling these resources can bypass intended limits. It is important to note that the issue resides in the framework's enforcement logic, not in the individual token content itself.

Is my system at risk if it uses MicroProfile JWT?

Halo Surface Signal indicates this is a high-priority concern because JAX-RS resources protected by MicroProfile JWT are frequently deployed as public-facing services. If your application handles authentication for internet-accessible APIs, your configuration is likely reachable and potentially affected by this bypass.

When should I take action for CVE-2026-111244?

You should prioritize this by identifying all applications using MicroProfile JWT. Confirm which services are exposed to the network and assess the sensitivity of the data they protect. The primary fix is to update to version 10.3.0 or 11.0.0-M2, which address the enforcement flaws.

References