Read the docs

Apache TomEE accepts expired MicroProfile JWT tokens with negative clock skew

Priority MEDIUM 46CWE-613Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-613.

Summary

Apache TomEE accepts a negative MicroProfile JWT clock skew setting without rejecting it, which disables validation of token expiration and other time-based claims. An attacker holding an expired token can authenticate with it in such configurations. Affected ranges are 10.0.0-M1 before 10.3.0 and 11.0.0-M1 before 11.0.0-M2. The weakness is CWE-613 (DEPRECATED: Insufficient Session Expiration), with a CVSS 3.1 base score of 9.1 (CRITICAL).

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

A negative MicroProfile JWT clock skew setting is not rejected and disables validation of the token expiration and other time-based claims. In such configurations, an attacker in possession of an expired token can still authenticate with it. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00142 3rd percentileScored 2026-11-16
Fix Fixed Apache TomEE (Apache Software Foundation): 10.3.0, 11.0.0-M2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache TomEE10.0.0-M1 to before 10.3.0; 11.0.0-M1 to before 11.0.0-M210.3.0, 11.0.0-M2Patch availableCNA
  • Apache TomEE VendorApache Affected 10.0.0-M1 to before 10.3.0; 11.0.0-M1 to before 11.0.0-M2 Fixed in 10.3.0, 11.0.0-M2 Patch available CNA

Remediation

Upgrade Apache TomEE to 10.3.0 or 11.0.0-M2, which fix the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA Apache TomEE (Apache Software Foundation) Fixed in 10.3.0, 11.0.0-M2

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Apache TomEE 10.3.0, 11.0.0-M2

    3 records Highest priority Priority MEDIUM 3 MEDIUM

    Other records, highest priority first

    • TI-2026-87750 Apache TomEE: Predictable OpenID Connect state and nonce valuesPriority MEDIUM 47
    • TI-2026-87802 EJB method authorization skipped in Apache TomEE on JDK 21+Priority MEDIUM 46

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-111243
  2. 2026-11-10 Alias added: GHSA-j9fc-pfc9-4gq6
  3. 2026-11-16 CVSS score added · CISA ADP
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2025-18529 Path equivalence in Apache Tomcat allows code execution via PUT KEVCVSS 3.1CRITICAL 10.0
  • TI-2024-30292 Forced browsing in Apache OFBiz bypasses controller-view authorization KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-26062 Incorrect authorization in Apache OFBiz exposes screen rendering code KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-21190 Path traversal in Apache OFBiz leads to remote code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-18186 Remote command execution in Apache HugeGraph-Server via Gremlin KEVCVSS 3.1CRITICAL 9.8
  • TI-2023-25106 Apache ActiveMQ OpenWire deserialization allows remote code execution KEVCVSS 3.1CRITICAL 10.0
See all 4172 →

Sources