CVE-2026-41883

Workarounds

Replace wildcard CDN mappings with explicit resource-to-URL mappings. For example, replace:

libraryName:*=https://cdn.example.com/*

with individual entries:

libraryName:resource1.js=https://cdn.example.com/resource1.js,
libraryName:resource2.js=https://cdn.example.com/resource2.js

Server-side EL injection leading to Remote Code Execution (RCE). Affects applications that use CDNResourceHandler with a wildcard CDN mapping (e.g. libraryName:*=https://cdn.example.com/*). An attacker can craft a resource request
URL containing an EL expression in the resource name, which is evaluated server-side.

The severity depends on the EL implementation and the objects available in the EL context. In the worst case this leads to Remote Code Execution (RCE). At minimum it allows information disclosure and denial of service.

Applications using CDNResourceHandler without wildcard mappings (i.e. only explicit resource-to-URL mappings) are not affected.

CVE-2026-41883 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.14.2, 2.7.32, 3.14.16, 4.7.5, 5.2.3); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed in versions 5.2.3, 4.7.5, 3.14.16, 2.7.32, and 1.14.2. Users should upgrade to the appropriate version for their branch.

1. What is CVE-2026-41883? CVE-2026-41883 is a high-severity security vulnerability in org.omnifaces:omnifaces (maven), affecting versions < 1.14.2. It is fixed in 1.14.2, 2.7.32, 3.14.16, 4.7.5, 5.2.3.
2. How severe is CVE-2026-41883? CVE-2026-41883 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.omnifaces:omnifaces are affected by CVE-2026-41883? org.omnifaces:omnifaces (maven) versions < 1.14.2 is affected.
4. Is there a fix for CVE-2026-41883? Yes. CVE-2026-41883 is fixed in 1.14.2, 2.7.32, 3.14.16, 4.7.5, 5.2.3. Upgrade to this version or later.
5. Is CVE-2026-41883 exploitable, and should I be worried? Whether CVE-2026-41883 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41883 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41883?
   • Upgrade org.omnifaces:omnifaces to 1.14.2 or later
   • Upgrade org.omnifaces:omnifaces to 2.7.32 or later
   • Upgrade org.omnifaces:omnifaces to 3.14.16 or later
   • Upgrade org.omnifaces:omnifaces to 4.7.5 or later
   • Upgrade org.omnifaces:omnifaces to 5.2.3 or later