CVE-2026-102695: omnifaces · Insufficient Verification of Data Authenticity
Affects omnifacesSource CVE Database V5
Not known to be exploited · CVSS 8.2 High · fixed in 5.4.2 : patch omnifaces soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-20.
- Patch
- Available – fixed in 5.4.2, 4.7.12, 3.14.23 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| omnifacesomnifaces | Affected
| Fixed in
|
| omnifacesomnifaces | Affected
| Fixed in
|
| omnifacesomnifaces | Affected
| Fixed in
|
| omnifacesomnifaces | Affected
| Fixed in
|
| omnifacesomnifaces | Affected
| Fixed in
|
Description
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.
References
- github.com/omnifaces/omnifaces/security/advisories/GHSA-fp43-vj7g-pg92 (opens in a new tab)
- github.com/omnifaces/omnifaces/commit/aa42da361821ddfbb85b126564e71587347d2786 (opens in a new tab)
- github.com/omnifaces/omnifaces/releases/tag/1.14.3 (opens in a new tab)
- github.com/omnifaces/omnifaces/releases/tag/2.7.33 (opens in a new tab)
- github.com/omnifaces/omnifaces/releases/tag/3.14.23 (opens in a new tab)
- github.com/omnifaces/omnifaces/releases/tag/4.7.12 (opens in a new tab)
- github.com/omnifaces/omnifaces/releases/tag/5.4.2 (opens in a new tab)