In Eclipse Mojarra versions 2.2.0 through 4.0.28, 4.1.0 through 4.1.19, and 5.0.0-M1 through 5.0.0-M11, when URL
Source GCVE Database
Not known to be exploited · CVSS 6.1 Medium · fixed in 5.0.0-M12 : update Eclipse Mojarra when convenient.
Data as of 4 Nov 2026, 16:43 UTC
Thin evidence
One scorer or none| CNA (eclipse) | CVSS 3.1 | 6.1 |
|---|
- Patch
- Available – fixed in 5.0.0-M12, 4.1.20, 4.0.29
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 4 Nov 2026.
What to do
Upgrade Eclipse Mojarra to 5.0.0-M12, 4.1.20 or 4.0.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse Mojarra | Affected
| Fixed in
|
| Eclipse FoundationEclipse Mojarra | Affected
| Fixed in
|
| Eclipse FoundationEclipse Mojarra | Affected
| Fixed in
|
Mavenorg.eclipse/mojarrapkg:maven/org.eclipse/mojarraOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, consider disabling URL client window mode or avoiding use of `h:button` components with untrusted input. Review application configurations related to `jakarta.faces.CLIENT_WINDOW_MODE` and `com.sun.faces.enableCspNonce` to mitigate risk.
Description
Eclipse Mojarra versions 2.2.0 through 4.0.28, 4.1.0 through 4.1.19, and 5.0.0-M1 through 5.0.0-M11 have a reflected cross-site scripting (XSS) vulnerability when URL client window mode is enabled. The client window id parameter is appended to URLs without URL-encoding, and the h:button component renders these URLs into JavaScript string literals. This allows an attacker to inject scripts that run on page load, bypassing Content Security Policy when nonce support is enabled.