CVE-2026-41883 — omnifaces
HIGHCVE-2026-41883 is a high-severity (CVSS 8.1) Expression Language Injection vulnerability in org.omnifaces:omnifaces. A fix is available for org.omnifaces:omnifaces — see the affected versions and patch details below.
OmniFaces: EL injection via crafted resource name in wildcard CDN mapping
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-2026-41883.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-41883 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifacesReal-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
Impact
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.
Patches
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.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.omnifaces:omnifaces | all versions | 1.14.2org.omnifaces:omnifaces:1.14.2 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 2.0-RC1&&< 2.7.32 | 2.7.32org.omnifaces:omnifaces:2.7.32 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 3.0-RC1&&< 3.14.16 | 3.14.16org.omnifaces:omnifaces:3.14.16 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 4.0-M1&&< 4.7.5 | 4.7.5org.omnifaces:omnifaces:4.7.5 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 5.0-M1&&< 5.2.3 | 5.2.3org.omnifaces:omnifaces:5.2.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.omnifaces:omnifaces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.omnifaces:omnifaces to 1.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41883 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-41883 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-41883. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-41883 in your dependencies?
O3 Security finds CVE-2026-41883 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.