CVE-2023-6236 is a high-severity (CVSS 7.3) CWE-345 vulnerability in org.wildfly.security:wildfly-elytron-http-oidc. A fix is available for org.wildfly.security:wildfly-elytron-http-oidc — see the affected versions and patch details below.
WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-6236.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.wildfly.security:wildfly-elytron-http-oidcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in Red Hat Enterprise Application Platform 8. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new "provider-url" option in addition to the "realm" option.
EAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly.security:wildfly-elytron-http-oidc | all versions | 2.2.5.Finalorg.wildfly.security:wildfly-elytron-http-oidc:2.2.5.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron-http-oidc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.security:wildfly-elytron-http-oidc to 2.2.5.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6236 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 8 | eap | RHSA-2024:3583 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8 | eap8-elytron-web-0:4.0.1-1.Final_redhat_00001.1.el8eap | RHSA-2024:3580 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9 | eap8-elytron-web-0:4.0.1-1.Final_redhat_00001.1.el9eap | RHSA-2024:3581 |
Frequently Asked Questions
Is CVE-2023-6236 in your dependencies?
Find it across Maven, including transitive dependencies.