CVE-2026-111243: A negative MicroProfile JWT clock skew setting is not rejected and disables validation of the token
Source GCVE Database
Not known to be exploited : upgrade to 11.0.0-M2 or 10.3.0 soon.
Data as of 10 Nov 2026, 19:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 11.0.0-M2, 10.3.0
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Apache TomEE and org.apache.tomee/mp-jwt to 11.0.0-M2 or 10.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache TomEEorg.apache.tomee:mp-jwt | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:mp-jwt | Affected
| Fixed in
|
Mavenorg.apache.tomee/mp-jwtpkg:maven/org.apache.tomee/mp-jwtOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.