Quick answers
- Is CVE-2026-102695 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102695 being exploited in the wild.
- How severe is CVE-2026-102695?
- High severity, with a CVSS score of 8.2, published 14 October 2026.
- Which products and versions are affected?
- OmniFaces before 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2.
- Is there a fix for CVE-2026-102695?
- Yes: fixed in 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102695 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102695?
- 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.
How to fix
- Fixed in: 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2
Technical details
CombinedResourceHandler accepts deflate+base64 encoded combined resource IDs without authenticity verification. Attackers can forge IDs to trigger unbounded decompression (leading to memory exhaustion), bypass jakarta.faces.RESOURCE_EXCLUDES to access Facelets sources and META-INF/resources, or exploit wildcard CDN mappings to cause blind server-side fetches with Host-header-derived destinations. The vulnerability does not enable arbitrary file read or arbitrary-scheme SSRF.
Affected products
- OmniFaces OmniFaces before 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2
Timeline
- 2026-10-14: disclosed