Vulnerabilities in pkg:maven/org.omnifaces/omnifaces

PACKAGE
Advisory Identifier: GHSA-fp43-vj7g-pg92
Advisory Summary

CVE-2026-102695 is a HIGH (CVSS 7.5) remote code execution vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting OmniFaces libraries in the Maven ecosystem. The issue involves forged combined-resource ids and related output/push boundaries. Remediation is available by upgrading affected packages to version 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.omnifaces/omnifaces

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.omnifaces/omnifaces. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fp43-vj7g-pg92 CVE-2026-102695 HIGH OmniFaces: Forged combined-resource IDs and related output/push boundaries
GHSA-vp6r-9m58-5xv8 CVE-2026-41883 HIGH OmniFaces: EL injection via crafted resource name in wildcard CDN mapping

CVE-2026-102695 at a Glance

CVE Identifier CVE-2026-102695
GHSA Identifier GHSA-fp43-vj7g-pg92
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product OmniFaces
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-102695

To remediate this vulnerability, upgrade all affected OmniFaces dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.omnifaces:omnifaces fixed: 1.14.3
<dependency>
    <groupId>org.omnifaces</groupId>
    <artifactId>omnifaces</artifactId>
    <version>1.14.3</version>
</dependency>
org.omnifaces:omnifaces fixed: 2.7.33
<dependency>
    <groupId>org.omnifaces</groupId>
    <artifactId>omnifaces</artifactId>
    <version>2.7.33</version>
</dependency>
org.omnifaces:omnifaces fixed: 3.14.23
<dependency>
    <groupId>org.omnifaces</groupId>
    <artifactId>omnifaces</artifactId>
    <version>3.14.23</version>
</dependency>
org.omnifaces:omnifaces fixed: 4.7.12
<dependency>
    <groupId>org.omnifaces</groupId>
    <artifactId>omnifaces</artifactId>
    <version>4.7.12</version>
</dependency>
org.omnifaces:omnifaces fixed: 5.4.2
<dependency>
    <groupId>org.omnifaces</groupId>
    <artifactId>omnifaces</artifactId>
    <version>5.4.2</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.omnifaces

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-102695, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.omnifaces

Analyze the terminal output to locate any version of OmniFaces in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.14.3), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.omnifaces command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In OmniFaces, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 demonstrated residual sink behavior. ## 2. Source-map cache With the documented optional source-map handler above a synthetic resource handler, 40 unique missing combined-resource requests grew the process-wide source-map cache from 13 to 92 entries. It has no size or eviction bound. This has a separate cache, configuration prerequisite, and fix from family 1. ## 3. HashParam callback output A URL-fragment value containing a single-quote JavaScript payload was stored by `o:hashParam` and later written unescaped into the Ajax callback script. On the follow-up Ajax render, real Chrome executed the canary `window.__omniXss=1337`. This requires a page using `o:hashParam` and the follow-up Ajax render. ## 4. Session/view push-channel replay A fresh WebSocket client with no HTTP cookie connected using a victim's session-scoped channel ID and received the victim's subsequent push. The code checks application-wide ID existence but does not bind the handshake to the current HTTP session, despite the documented current-session guarantee. The UUID remains an unguessable bearer-token prerequisite; this is replay after token exposure, not brute force. ## 5. Push idle-connection and fanout behavior Twelve independent clients joined one application-scoped channel and all 12 received the same push. Current code sets every accepted session's maximum idle timeout to zero, retains sessions in an unbounded per-channel queue, and walks the full queue on each push. I am reporting the demonstrated mechanism as a bounded design weakness: container connection limits remain an outer bound, and I am not claiming unbounded heap growth from the 12-client test. ## Intentionally excluded leads - A duplicate-Range response-amplification lead was disproved. Twenty-four ranges produced only one response body because the stream wrapper closes after the first range. I am not reporting it as a security issue. - The older `Servlets.facesRedirect` XML issue is fixed on the current branch. I am not reporting it as a new current-upstream issue. ## Expected invariants - Only server-issued combined IDs should be accepted; decoding and caches should be bounded; excluded resources and dynamic handlers should not become attacker-selected inner resources. - Dynamic URLs should not derive an outbound destination from an untrusted `Host` header. - Source-map lookups should not create unbounded process-lifetime state. - `HashParam` values must be escaped for a JavaScript string inside an XML CDATA callback. - Session/view push subscriptions should be bound to the owning HTTP session or authenticated principal; idle limits and per-channel caps should remain operator-controllable. ## Suggested fixes and available evidence - Authenticate generated combined IDs with a per-deployment secret, cap inflated output, bound the combined cache, and avoid caching failed loads. - Require an existing/registered inner resource before wildcard remapping and reject excluded resource types at serve time. - Derive dynamic-resource origins from trusted configuration rather than the request `Host` value. - Bound or evict the source-map cache. - Apply JavaScript-string plus CDATA-safe encoding to `HashParam` callback values. - Capture and verify HTTP-session or principal ownership during the WebSocket handshake; retain a finite idle timeout and configurable per-channel limits. Daniel Birtwhistle

CVE-2026-102695 Affected OmniFaces Versions

5 component(s)
Fixed Versions:
1.14.32.7.333.14.234.7.125.4.2
Product / Package Ecosystem Affected Versions Fixed Version
org.omnifaces:omnifaces
Maven
< 1.14.3
1.14.3
org.omnifaces:omnifaces
Maven
≥ 2.0.0
< 2.7.33
2.7.33
org.omnifaces:omnifaces
Maven
≥ 3.0.0
< 3.14.23
3.14.23
org.omnifaces:omnifaces
Maven
≥ 4.0.0
< 4.7.12
4.7.12
org.omnifaces:omnifaces
Maven
≥ 5.0.0
< 5.4.2
5.4.2

References

Frequently Asked Questions

What is CVE-2026-102695?
CVE-2026-102695 is a security vulnerability in OmniFaces involving Forged combined-resource IDs and related output/push boundaries under CWE-345: Insufficient Verification of Data Authenticity.
Which OmniFaces versions are affected?
Affected versions include releases prior to 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2 across affected packages: org.omnifaces:omnifaces.
What version fixes CVE-2026-102695?
Upgrading to 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is omnifaces affected?
Yes, org.omnifaces:omnifaces is affected in releases prior to 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2. Upgrade your dependency to 1.14.3, 2.7.33, 3.14.23, 4.7.12, 5.4.2 or later.
What is the CVSS score of CVE-2026-102695?
CVE-2026-102695 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-102695?
CVE-2026-102695 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Maven dependencies for CVE-2026-102695?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.omnifaces'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fp43-vj7g-pg92",
  "modified" : "2026-10-14T15:58:54Z",
  "published" : "2026-07-24T22:35:27Z",
  "aliases" : [ "CVE-2026-102695" ],
  "summary" : "OmniFaces: Forged combined-resource IDs and related output/push boundaries",
  "details" : "## 1. Forged combined-resource IDs\n`CombinedResourceInfo` accepts a path-derived ID without an authenticity check,\ninflates it without an output limit, converts it to attacker-selected resource\nidentifiers, and retains unique IDs in an unbounded static cache. In bounded\ntests, 20,754 encoded bytes inflated to 16,000,000 characters (about 770:1;\nabout 49 MB observed heap delta), and 200 unique IDs added 200 permanent cache\nentries. A legitimately shaped short ID remained about 1:1, while malformed\ninput was rejected; the missing distinction is between a server-issued ID and\nan attacker-minted but structurally valid ID.\n\nThe minimal application also confirmed three sink tails from the same forged-ID\nroot:\n\n- A wildcard CDN mapping performed a server-side fetch and relayed the exact\n  loopback-canary body. This requires the documented combined-resource and\n  wildcard-CDN configuration.\n- A forged inner `.xhtml` resource bypassed the excluded-resource boundary and\n  returned its raw content.\n- A forged `omnifaces.graphic` inner resource plus a canary `Host` header caused\n  an outbound GET to that host. This result is blind and deployment-dependent;\n  I am not claiming arbitrary-scheme or arbitrary-destination SSRF.\n\nThese behaviors reproduce after the fix for CVE-2026-41883 /\nGHSA-vp6r-9m58-5xv8. That advisory concerned EL evaluation order in the wildcard\nCDN path. This report has a different root: unsigned combined IDs and missing\ndecode/cache bounds, with separately demonstrated residual sink behavior.\n\n## 2. Source-map cache \n\nWith the documented optional source-map handler above a synthetic resource\nhandler, 40 unique missing combined-resource requests grew the process-wide\nsource-map cache from 13 to 92 entries. It has no size or eviction bound. This\nhas a separate cache, configuration prerequisite, and fix from family 1.\n\n## 3. HashParam callback output\n\nA URL-fragment value containing a single-quote JavaScript payload was stored by\n`o:hashParam` and later written unescaped into the Ajax callback script. On the\nfollow-up Ajax render, real Chrome executed the canary\n`window.__omniXss=1337`. This requires a page using `o:hashParam` and the\nfollow-up Ajax render.\n\n## 4. Session/view push-channel replay \n\nA fresh WebSocket client with no HTTP cookie connected using a victim's\nsession-scoped channel ID and received the victim's subsequent push. The code\nchecks application-wide ID existence but does not bind the handshake to the\ncurrent HTTP session, despite the documented current-session guarantee. The\nUUID remains an unguessable bearer-token prerequisite; this is replay after\ntoken exposure, not brute force.\n\n## 5. Push idle-connection and fanout behavior \n\nTwelve independent clients joined one application-scoped channel and all 12\nreceived the same push. Current code sets every accepted session's maximum idle\ntimeout to zero, retains sessions in an unbounded per-channel queue, and walks\nthe full queue on each push. I am reporting the demonstrated mechanism as a\nbounded design weakness: container connection limits remain an outer bound,\nand I am not claiming unbounded heap growth from the 12-client test.\n\n## Intentionally excluded leads\n\n- A duplicate-Range response-amplification lead was disproved. Twenty-four\n  ranges produced only one response body because the stream wrapper closes\n  after the first range. I am not reporting it as a security issue.\n- The older `Servlets.facesRedirect` XML issue is fixed on the current branch.\n  I am not reporting it as a new current-upstream issue.\n\n## Expected invariants\n\n- Only server-issued combined IDs should be accepted; decoding and caches\n  should be bounded; excluded resources and dynamic handlers should not become\n  attacker-selected inner resources.\n- Dynamic URLs should not derive an outbound destination from an untrusted\n  `Host` header.\n- Source-map lookups should not create unbounded process-lifetime state.\n- `HashParam` values must be escaped for a JavaScript string inside an XML\n  CDATA callback.\n- Session/view push subscriptions should be bound to the owning HTTP session or\n  authenticated principal; idle limits and per-channel caps should remain\n  operator-controllable.\n\n## Suggested fixes and available evidence\n\n- Authenticate generated combined IDs with a per-deployment secret, cap\n  inflated output, bound the combined cache, and avoid caching failed loads.\n- Require an existing/registered inner resource before wildcard remapping and\n  reject excluded resource types at serve time.\n- Derive dynamic-resource origins from trusted configuration rather than the\n  request `Host` value.\n- Bound or evict the source-map cache.\n- Apply JavaScript-string plus CDATA-safe encoding to `HashParam` callback\n  values.\n- Capture and verify HTTP-session or principal ownership during the WebSocket\n  handshake; retain a finite idle timeout and configurable per-channel limits.\n\nDaniel Birtwhistle",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.omnifaces:omnifaces"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.14.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.omnifaces:omnifaces"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.7.33"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.omnifaces:omnifaces"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.14.23"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.omnifaces:omnifaces"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.7.12"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.omnifaces:omnifaces"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0"
      }, {
        "fixed" : "5.4.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/security/advisories/GHSA-fp43-vj7g-pg92"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/commit/59d6c5188c39418546fe500d05036645987a77d1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/commit/a52b92461cf39d983f51ce8724fe7e6b944073e4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/commit/aa42da361821ddfbb85b126564e71587347d2786"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/commit/c43eef01174a4dc09cec44eff553ff6284150af7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnifaces/omnifaces/commit/d5cae243c4692555efaa4ba774e0f8f60e3f4db5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/omnifaces/omnifaces"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345", "CWE-770", "CWE-79", "CWE-862" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T22:35:27Z",
    "nvd_published_at" : null
  }
}