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-2026-111243
UNRATEDCVSS · not yet scored
Also known asEUVD-2026-121249 (ENISA EUVD) · GHSA-j9fc-pfc9-4gq6 (GitHub Security Advisories)Source: ENISA EUVD
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS v2: —Exploit: None knownExposed services: Not assessed
The CVE record names the fixed release — apply it.
- CVSS
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
- EG Severity
- Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 10, 2026
Last Modified
November 12, 2026
References (1)
- security@apachehttps://lists.apache.org/thread/zb9sshs1fhz72llk3bb20ksw50n9jhqpVendor Advisory
Vendor Advisories for CVE-2026-111243(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-12 17:09 UTCEchelonGraph re-scored
- 2026-11-12 17:09 UTCGHSA enrichmentGHSA-j9fc-pfc9-4gq6
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-10 18:59 UTCGHSA enrichmentGHSA-j9fc-pfc9-4gq6
- 2026-11-10 16:27 UTCNVD update
- 2026-11-10 16:00 UTCENISA EUVD ID recordedEUVD-2026-121249 · Source: ENISA EUVD
- 2026-11-10 15:35 UTCEchelonGraph re-scored
- 2026-11-10 15:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-111243?
CVE-2026-111243 is a vulnerability whose severity is not yet rated; its CVE record was published on November 10, 2026. 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…
When was the CVE record for CVE-2026-111243 published?
The CVE record for CVE-2026-111243 was published on November 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-111243 actively exploited?
CVE-2026-111243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-111243?
The CVE record for CVE-2026-111243 names the fix: "Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue." The vendor advisories EchelonGraph has for CVE-2026-111243 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-111243
Is Your Infrastructure Affected by CVE-2026-111243?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.