How severe is CVE-2026-41883?

CVE-2026-41883 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-41883?

CVE-2026-41883 affects the following packages: org.omnifaces:omnifaces (Maven), org.omnifaces:omnifaces (Maven), org.omnifaces:omnifaces (Maven), org.omnifaces:omnifaces (Maven), org.omnifaces:omnifaces (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-41883?

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.

How do I detect CVE-2026-41883 in my Maven dependencies?

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.

How do I mitigate CVE-2026-41883 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-41883 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41883 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-41883?

CVE-2026-41883 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-41883?

CVE-2026-41883 is classified as Expression Language Injection (CWE-917). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-41883 published, and has it been updated?

CVE-2026-41883 was published on May 8, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-41883 — omnifaces

HIGH

CVE-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

Also known asGHSA-vp6r-9m58-5xv8

Published

May 8, 2026

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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

5 pkgs affected

☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces☕org.omnifaces:omnifaces

Real-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

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.omnifaces:omnifaces`	all versions	1.14.2`org.omnifaces:omnifaces:1.14.2`
☕Maven	`org.omnifaces:omnifaces`	≥ 2.0-RC1&&< 2.7.32	2.7.32`org.omnifaces:omnifaces:2.7.32`
☕Maven	`org.omnifaces:omnifaces`	≥ 3.0-RC1&&< 3.14.16	3.14.16`org.omnifaces:omnifaces:3.14.16`
☕Maven	`org.omnifaces:omnifaces`	≥ 4.0-M1&&< 4.7.5	4.7.5`org.omnifaces:omnifaces:4.7.5`
☕Maven	`org.omnifaces:omnifaces`	≥ 5.0-M1&&< 5.2.3	5.2.3`org.omnifaces:omnifaces:5.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
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
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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` withou