Skip to main content
cve.nowby Sazabi
← Vulnerabilities
CVE-2026-111243

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

Exploited
No known exploitation
Fix
Fixed in 10.3.0, 11.0.0-M2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 10.3.0, 11.0.0-M2.

Published
Last modified
Reference
Last checked
11/100 · provisional
Low (apache)
None on Exploit-DB, Metasploit or GitHub

Summary

Apache TomEE accepts expired MicroProfile JWT tokens when a negative clock skew setting is configured, because that setting disables checks on token expiration and other time-based claims. An attacker holding an expired token can use it to authenticate.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original 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.

cve.now Index

11Pcve.now Index 11 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity1/10Rated low by apache
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

  • Upgrade to a fixed version: 10.3.0, 11.0.0-M2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-111243 (Apache TomEE: Expired MicroProfile JWT tokens accepted with negative clock skew), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-111243 (entry last updated 2026-11-10):
Affected:
- Maven package org.apache.tomee:mp-jwt: from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2
Fixed versions: 10.3.0, 11.0.0-M2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111243 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111243 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/zb9sshs1fhz72llk3bb20ksw50n9jhqp
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-111243
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-111243.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-111243

Is CVE-2026-111243 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-111243?

org.apache.tomee:mp-jwt (Maven): from 10.0.0-M1 before 10.3.0; from 11.0.0-M1 before 11.0.0-M2.Source: cve.now feed data

How do I fix CVE-2026-111243?

Upgrade to a fixed version: 10.3.0, 11.0.0-M2.Source: cve.now feed data

Sources

Related

More vulnerabilities