How to Fix CVE-2026-35092: Red Hat Enterprise Linux 10 (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 7.5, High |
|---|---|
| Actively exploited? | No |
| Affected | Red Hat Enterprise Linux 10 (0:3.1.9-2.el10_1.1 < *); Red Hat Enterprise Linux 10 (0:3.1.10-1.el10_2.1 < *); Red Hat Enterprise Linux 10.0 Extended Update Support (0:3.1.9-1.el10_0.2 < *) |
| Fixed in | Same patched build as CVE-2026-4631 |
| Type (CWE) | CWE-190: Integer Overflow or Wraparound |
CVE-2026-35092 is a sibling vulnerability in the same Red Hat Red Hat Enterprise Linux 10 advisory bundle as CVE-2026-4631. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-35092 matches the primary write-up.
What is different about CVE-2026-35092?
A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service.
Impact is consistent with the bundle: a denial-of-service condition that crashes or hangs the affected service. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-35092
Apply the patched build per the primary write-up: How to Fix CVE-2026-4631.
For a quick check, confirm the running version of Red Hat Enterprise Linux 10:
# Confirm the installed version via your package manager
dpkg -l | grep -i red # Debian/Ubuntu
rpm -qa | grep -i red # RHEL/CentOS/Rocky
Frequently asked questions
Is CVE-2026-35092 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-35092?
CVSS rates it 7.5 (High). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Red Hat Enterprise Linux 10 offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-35092 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://access.redhat.com/errata/RHSA-2026:13644
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-35092
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-4631
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Red Hat Red Hat Enterprise Linux 10 advisory bundle. Full procedure at how-to-fix-cve-2026-4631.*