CVE-2026-111260 · Package
NO FIX YET · SEE WHAT TO DO
The Jakarta Security OpenID Connect authentication mechanism generates its state and nonce values with a non-cryptographic random number generator and too little entropy. A remote attacker who predicts these values can forge an authentication callback that logs a victim into the attacker's account, and ID token replay protection is weakened.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that use the Jakarta Security OpenID Connect authentication mechanism for sign-in on a Jakarta EE server. Applications that do not use this mechanism, or that use a different login method, are not exposed through this flaw.
Not affected if not-using-openid-connect, other-auth-mechanism
Who cares jakarta-ee, java, openid-connect
pom.xml or build.gradle) and see whether it is below 10.3.0 or 11.0.0-M210.3.0 or 11.0.0-M2, which the sources state fix the issueThe Jakarta Security OpenID Connect authentication mechanism generates the state and nonce values with a non-cryptographic random number generator and insufficient entropy. A remote attacker who predicts these values can forge an authentication callback that logs a victim into the attacker's account, and the replay protection for ID tokens is weakened. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.