Skip to main content
VulnerabilityPublished

CVE-2026-109549: OmniFaces · SSE push channels are not bound to their owning HTTP session

Affects org.omnifaces:omnifacesSource GCVE Database

0
Compare
Authoritative record:CVE-2026-109549· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 5.4.3 when convenient.

Data as of 19 Nov 2026, 21:06 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.9
Patch
Available – fixed in 5.4.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade org.omnifaces:omnifaces to 5.4.3.

Affected software

ProductAffectedFixed in
Mavenorg.omnifaces:omnifacesAffected
  • >=5.2.0 <5.4.3
Fixed in
  • 5.4.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OmniFaces to version 5.4.3 or later, where the SSE push transport enforces HTTP session ownership checks for session- and view-scoped channels, aligning with the WebSocket push channel fix. Until patched, avoid exposing session- or view-scoped SSE channel IDs or consider disabling SSE push transport if feasible. No other mitigations are documented.

Description

OmniFaces versions 5.2.0 up to but not including 5.4.3 contain a vulnerability in the Server-Sent Events (SSE) push transport where SSE push channels are not properly bound to their owning HTTP session. This allows a leaked session- or view-scoped SSE channel ID to be reused from any HTTP session or even without a session, enabling unauthorized access to pushed messages. The issue was fixed in version 5.4.3 by binding SSE channels to their HTTP sessions, similar to the previously fixed WebSocket push channels.

References

Community reviews

Loading reviews…