CVE-2026-102695

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-24) is not newer than that change (2026-10-20), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-101293 (ENISA EUVD) · GHSA-fp43-vj7g-pg92 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 20, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Forged combined resource IDs are accepted without authenticity check · Advisory · omnifaces/omnifaces · GitHub

Affected: 5.4.3

https://github.com/omnifaces/omnifaces/security/advisories/GHSA-fp43-vj7g-pg92
GitHub commit

commit aa42da361821 (omnifaces/omnifaces)

Fix landed in omnifaces/omnifaces commit aa42da361821 — awaiting tagged release

https://github.com/omnifaces/omnifaces/commit/aa42da361821ddfbb85b126564e71587347d2786

Vendor Advisories for CVE-2026-102695(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.omnifaces:omnifaces @ 1.14.3 (fixes < 1.14.3)—ghsa
mavenorg.omnifaces:omnifaces @ 2.7.33 (fixes >= 2.0.0, < 2.7.33)—ghsa
mavenorg.omnifaces:omnifaces @ 3.14.23 (fixes >= 3.0.0, < 3.14.23)—ghsa
mavenorg.omnifaces:omnifaces @ 4.7.12 (fixes >= 4.0.0, < 4.7.12)—ghsa
mavenorg.omnifaces:omnifaces @ 5.4.2 (fixes >= 5.0.0, < 5.4.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.omnifaces:omnifaces1.1 ... 1.8.3 (27 versions)
  • every version up to 1.14.3: fixed in 1.14.3
  • 2.0.0 up to 2.7.33: fixed in 2.7.33
  • 3.0.0 up to 3.14.23: fixed in 3.14.23
  • 4.0.0 up to 4.7.12: fixed in 4.7.12
  • 5.0.0 up to 5.4.2: fixed in 5.4.2
—

Weakness Classification(6)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-fp43-vj7g-pg92 · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-27 18:56 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-25 14:56 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-20 02:26 UTCEG score recompute
  19. 2026-10-20 01:54 UTCEG score recompute
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-18 05:10 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-16 20:09 UTCEG score recompute
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 4 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-14 17:14 UTCEG score recompute
  3. 2026-10-14 16:11 UTCEG score recomputeFirst assessed: 8.2 HIGH
  4. 2026-10-14 16:09 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

Maven:org.omnifaces:omnifaces

Frequently asked(5)

What is CVE-2026-102695?
CVE-2026-102695 is a high-severity vulnerability; its CVE record was published on October 14, 2026. 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…
When was the CVE record for CVE-2026-102695 published?
The CVE record for CVE-2026-102695 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-102695 actively exploited?
CVE-2026-102695 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102695?
CVE-2026-102695 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102695?
A fix for CVE-2026-102695 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102695 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102695

Explore →

Is Your Infrastructure Affected by CVE-2026-102695?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs