Skip to content
Fencer Intel
low —

CVE-2026-111243 json

Apache TomEE: Expired MicroProfile JWT tokens accepted with negative clock skew

published yesterday modified yesterday also EUVD-2026-121249

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.tomee:mp-jwt 10.3.0, 11.0.0-M2
  • Apache Software Foundation Apache TomEE 10.3.0, 11.0.0-M2

Is CVE-2026-111243 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected packages

ecosystem package affected fixed in
maven org.apache.tomee:mp-jwt
>=10.0.0-M1, <10.3.0
>=11.0.0-M1, <11.0.0-M2
10.3.0
11.0.0-M2

Affected products

  • Apache Software Foundation Apache TomEE

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.