OmniFaces multiple vulnerabilities in resource handling and push channels

Severity: high · CVSS 7.5 · Published 2026-07-24

OmniFaces, a utility library for JavaServer Faces (JSF), contains multiple vulnerabilities that can impact application stability and security. Attackers can trigger excessive memory consumption (denial of service) by forging resource identifiers, execute malicious scripts in a user's browser (XSS), or intercept real-time data updates intended for other users. These issues could lead to service outages, unauthorized data access, or full account compromise depending on the application's configuration.

Technologies: OmniFaces. Vendors: OmniFaces.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
High severity, with a CVSS score of 7.5, published 24 July 2026.
Which products and versions are affected?
OmniFaces < 1.14.3, >= 2.0.0, < 2.7.33, >= 3.0.0, < 3.14.23, >= 4.0.0, < 4.7.12, >= 5.0.0, < 5.4.2.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network, in a software library.
Am I affected?
Check whether you run OmniFaces at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

OmniFaces is affected by several distinct vulnerabilities. 1) CombinedResourceInfo lacks authenticity checks for path-derived IDs, allowing attackers to forge IDs that cause massive heap inflation and unbounded static cache growth (DoS). 2) The source-map handler lacks size or eviction bounds, leading to memory exhaustion. 3) o:hashParam fails to escape URL-fragment values before writing them to Ajax callback scripts, enabling Cross-Site Scripting (XSS). 4) The WebSocket push-channel implementation fails to bind handshakes to the current HTTP session, allowing replay of session-scoped channel IDs if the UUID is exposed. 5) Push-channel queues are unbounded and set idle timeouts to zero, creating a design weakness for resource exhaustion. Patches are available in versions 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2.

Affected products

  • omnifaces omnifaces < 1.14.3, >= 2.0.0, < 2.7.33, >= 3.0.0, < 3.14.23, >= 4.0.0, < 4.7.12, >= 5.0.0, < 5.4.2

Timeline

  • 2026-07-23: disclosed: Initial disclosure by Daniel Birtwhistle
  • 2026-07-24: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.