Categories
CVE-2026-102695 high CVSS 8.2

Vulnerability in org.omnifaces:omnifaces (CVE-2026-102695)

Summary

Vulnerability in org.omnifaces:omnifaces (CVE-2026-102695). Risk of unauthorized operations or information disclosure. Exploitable via CombinedResourceInfo. Mitigation: upgrade to 5.4.2 or later.

Original description

The description as published by the source.

1. Forged combined-resource IDs

CombinedResourceInfo accepts a path-derived ID without an authenticity check,
inflates it without an output limit, converts it to attacker-selected resource
identifiers, and retains unique IDs in an unbounded static cache. In bounded
tests, 20,754 encoded bytes inflated to 16,000,000 characters (about 770:1;
about 49 MB observed heap delta), and 200 unique IDs added 200 permanent cache
entries. A legitimately shaped short ID remained about 1:1, while malformed
input was rejected; the missing distinction is between a server-issued ID and
an attacker-minted but structurally valid ID.

The minimal application also confirmed three sink tails from the same forged-ID
root:

  • A wildcard CDN mapping performed a server-side fetch and relayed the exact
    loopback-canary body. This requires the documented combined-resource and
    wildcard-CDN configuration.
  • A forged inner .xhtml resource bypassed the excluded-resource boundary and
    returned its raw content.
  • A forged omnifaces.graphic inner resource plus a canary Host header caused
    an outbound GET to that host. This result is blind and deployment-dependent;
    I am not claiming arbitrary-scheme or arbitrary-destination SSRF.

These behaviors reproduce after the fix for CVE-2026-41883 /
GHSA-vp6r-9m58-5xv8. That advisory concerned EL evaluation order in the wildcard
CDN path. This report has a different root: unsigned combined IDs and missing
decode/cache bounds, with separately demonstrate…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-102695 has been found in org.omnifaces:omnifaces.
Attackers can target a specific entry point like CombinedResourceInfo over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.2/10.
What to do: upgrade org.omnifaces:omnifaces to 5.4.2 or later.
If unsure, ask your IT team or search "org.omnifaces:omnifaces CVE-2026-102695" on the vendor's site.

CVE-2026-102695 (org.omnifaces:omnifaces) — CWE-345 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CombinedResourceInfo / omnifaces.graphic / Host / Servlets.facesRedirect
Patched: 5.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-345) exists in org.omnifaces:omnifaces. Attackers reach the vulnerable code path via CombinedResourceInfo without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.omnifaces:omnifaces. Attack surface: CombinedResourceInfo / omnifaces.graphic / Host / Servlets.facesRedirect.

🔥 Severity

Severity: High (CVSS 8.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.4.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.omnifaces:omnifaces を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.omnifaces:omnifaces to 5.4.2

    ステージング環境で 5.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.omnifaces:omnifaces
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details