Skip to main content
VulnerabilityPublished

CVE-2026-111260: Apache TomEE · PRNG

Affects Apache TomEESource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 11.0.0-M2 or 10.3.0 soon.

Data as of 10 Nov 2026, 15:34 UTC

Severity
High

Rated High by Threat Radar's AI analysis · 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

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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/tomee-security to 11.0.0-M2 or 10.3.0.

Affected software

ProductAffectedFixed in
Apache TomEEorg.apache.tomee:tomee-securityAffected
  • >=11.0.0-M1 <11.0.0-M2
Fixed in
  • 11.0.0-M2
Apache TomEEorg.apache.tomee:tomee-securityAffected
  • >=10.0.0-M2 <10.3.0
Fixed in
  • 10.3.0
Mavenorg.apache.tomee/tomee-securitypkg:maven/org.apache.tomee/tomee-securityOther threatsAffected
  • >=10.0.0-M2 <10.3.0
  • >=11.0.0-M1 <11.0.0-M2
Fixed in
  • 10.3.0
  • 11.0.0-M2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache TomEE to versions 10.3.0 or 11.0.0-M2, which contain fixes for this vulnerability. No other mitigation is indicated by the vendor advisory.

Description

Apache TomEE's Jakarta Security OpenID Connect authentication mechanism used a non-cryptographic pseudo-random number generator to create state and nonce values, resulting in insufficient entropy. This weakness allows a remote attacker to predict these values and forge authentication callbacks, potentially logging victims into attacker-controlled accounts and weakening ID token replay protection. The issue is fixed in versions 10.3.0 and 11.0.0-M2.

References

Community reviews

Loading reviews…