GHSA-vp6r-9m58-5xv8
HIGHGHSA-vp6r-9m58-5xv8 is a high-severity (CVSS 8.1) Expression Language Injection vulnerability in org.omnifaces:omnifaces. O3 Security confirms whether GHSA-vp6r-9m58-5xv8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OmniFaces: EL injection via crafted resource name in wildcard CDN mapping
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.2 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 2.0-RC1&&< 2.7.32 | 2.7.32 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 3.0-RC1&&< 3.14.16 | 3.14.16 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 4.0-M1&&< 4.7.5 | 4.7.5 |
| ☕Maven | org.omnifaces:omnifaces | ≥ 5.0-M1&&< 5.2.3 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-vp6r-9m58-5xv8 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 pinpoints whether GHSA-vp6r-9m58-5xv8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vp6r-9m58-5xv8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vp6r-9m58-5xv8 in your dependencies?
O3 detects GHSA-vp6r-9m58-5xv8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.