CVE-2026-102695

8.2High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

8.2High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: High impact on availability
Weakness: CWE-345, CWE-409, CWE-552

Impact

Remote unauthenticated attackers can crash the application via memory exhaustion, leak Facelets source code from webapp resources or META-INF, and potentially trigger limited blind SSRF requests. An attacker only needs network access to send crafted requests containing forged resource IDs.

Root cause

CombinedResourceHandler parses deflated and base64-encoded resource IDs without verifying their server-side authenticity and bypasses standard RESOURCE_EXCLUDES checks.

Affected systems

OmniFaces before 1.14.3, 2.7.33, 3.14.23, 4.7.12, and 5.4.2

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Fix & remediation

Upgrade OmniFaces dependency to 1.14.3, 2.7.33, 3.14.23, 4.7.12, or 5.4.2 according to your major release train. No workaround is documented; prioritize updating the library.

shell

$ mvn dependency:tree | grep omnifaces

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD 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

Source: nvd.nist.gov/vuln/detail/CVE-2026-102695