Skip to content
Fencer Intel
high 7.8

CVE-2026-109092 json

X.Org Server XvShmPutImage Shared-Memory Bounds Overflow

published yesterday modified yesterday also EUVD-2026-125400

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

Incorrectly handled negative sizes when processing ProcXvShmPutImage requests in the X.Org xwayland before 24.1.15 and X Server before 21.1.26 could be used by local authenticated X clients to crash the X server or execute code.

Patch / fix

  • X.Org xwayland 24.1.15
  • X.Org xorg-x11-server 21.1.26
  • xorg-x11-server SLE High Performance Computing 15 SP4-ESPOS, SLES for SAP 15 SP4, SLES 15 SP4-LTSS +1 more 1.20.3-150400.38.80.1
  • xorg-x11-server SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 1.19.6-10.117.1

suse advisories SUSE-SU-2026:5180-1SUSE-SU-2026:5178-1

  • xorg-x11-server openSUSE Leap 16.0 21.1.15-160000.7.1
  • xorg-x11-server openSUSE Tumbleweed 21.1.25-2.1
  • xwayland openSUSE Tumbleweed 24.1.14-2.1

opensuse advisories openSUSE-SU-2026:22274-1openSUSE-SU-2026:12534-1openSUSE-SU-2026:12535-1

  • xwayland Alpine 3.24 24.1.15-r0
  • xorg-server Alpine 3.24 21.1.26-r0

alpine advisories ALPINE-CVE-2026-109092

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-109092 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • X.Org xwayland
  • X.Org xorg-x11-server

Classification

Weakness
  • CWE-191 Integer Underflow (Wrap or Wraparound)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.