Read the docs
TI-2026-74169 Aliases CVE-2026-102695

OmniFaces accepts forged combined resource IDs without verification

Priority MEDIUM 41CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass, Information disclosure
Confidentiality · integrity · availability
Low · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-345 and CWE-552.

Summary

OmniFaces versions before 1.14.3, from 2.0 before 2.7.33, from 3.0 before 3.14.23, from 4.0 before 4.7.12, and from 5.0 before 5.4.2 are affected. The CombinedResourceHandler accepts a combined resource ID without verifying that the server issued it (CWE-345). A remote unauthenticated attacker can send a forged ID to exhaust server memory and disclose Facelets source files from the web application resource tree.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

OmniFaces is a utility library for Faces. In OmniFaces versions before 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2, CombinedResourceHandler accepts a structurally valid deflated and base64 encoded combined resource ID without verifying that the server issued it. A forged ID can cause unbounded decoded output, add unique reconstructed IDs to a process-lifetime cache, or combine resources other than stylesheets and scripts. Because jakarta.faces.RESOURCE_EXCLUDES is not applied by this custom resolution path, a forged ID can disclose Facelets source from the webapp resource tree or META-INF/resources. In a deployment configured with the wildcard CDN mapping, a forged ID that selects omnifaces.graphic can also cause a blind, deployment-dependent server-side fetch whose destination derives partly from the request Host header. The flaw does not provide arbitrary file read or establish arbitrary-scheme or arbitrary-destination SSRF. The shared authenticity failure permits memory exhaustion and limited resource disclosure. This issue is fixed in versions 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00306 23rd percentileScored 2026-11-07
Fix Fixed omnifaces (omnifaces): 1.14.3, 2.7.33, 3.14.23 +2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
omnifacesomnifacesbefore 1.14.3; 2.0 to before 2.7.33; 3.0 to before 3.14.23; 4.0 to before 4.7.12; 5.0 to before 5.4.21.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2Patch availableCNA
  • omnifaces Vendoromnifaces Affected before 1.14.3; 2.0 to before 2.7.33; 3.0 to before 3.14.23; 4.0 to before 4.7.12; 5.0 to before 5.4.2 Fixed in 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2 Patch available CNA

Remediation

Upgrade OmniFaces to version 1.14.3, 2.7.33, 3.14.23, 4.7.12, or 5.4.2, matching the release line in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA omnifaces (omnifaces) Fixed in 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-14 Threatist record created from CVE-2026-102695
  2. 2026-10-16 Priority changed: MEDIUM → LOW
  3. 2026-10-20 CISA SSVC decision points changed
  4. 2026-10-20 Priority changed: LOW → MEDIUM
  5. 2026-11-06 Affected versions changed · Red Hat
  6. 2026-11-06 CVSS score added · Red Hat

References

  • TI-2026-30287 OmniFaces: EL injection via crafted resource name in wildcard CDN mapping CVSS 3.1HIGH 8.1

Sources