Red Hat denial of service in Corosync via heap overflow
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
Corosync, as packaged in Red Hat Enterprise Linux and several OpenShift Container Platform images, has a heap-based buffer overflow in how it handles membership commit tokens. An attacker on an adjacent network who has high-level privileges can send a crafted, oversized commit token to a node in the GATHER membership state, corrupting memory and causing a denial of service.
Written by a model
Original description
A heap-based buffer overflow was found in Corosync's Totem SRP membership commit token handling. The sanity check for memb_commit_token messages validates only minimum length and address-entry counts, not an upper bound against the fixed commit_token_storage buffer. A network-adjacent attacker who can deliver a crafted oversized commit token to a node in the GATHER membership state may overflow the heap-allocated totemsrp instance, leading to memory corruption and denial of service.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133475 (Corosync: corosync: heap-based buffer overflow in memb_commit_token handling when msg_len exceeds commit_token_storage), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133475 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133475 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133475 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2577435
- https://access.redhat.com/security/cve/CVE-2026-133475
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133475
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133475"}.Affected versions
- corosync
- corosync
- corosync
- corosync
- openshift/ose-rhel-coreos-9
- rhcos
- openshift/ose-rhel-coreos-10
- openshift/ose-rhel-coreos-9
- rhcos
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity5.7/10CVSS 5.7
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133475 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2577435 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-133475 |
Related
- CVE-2026-130644Ansible-core: ansible-core: ansible-galaxy collection install path traversal via unvalidated artifact-derived collection name allows file…
- CVE-2026-105929Ansible-core: ansible-galaxy role install path traversal via unvalidated role name allows file writes and directory deletion outside the…
- CVE-2026-133553Crun: crun: tmpcopyup follows a second path lookup and copies image files onto the host
- CVE-2026-132858Gdm: missing authorization on createremotedisplay allows autologin as arbitrary users, including root
- CVE-2026-132150Gimp: out-of-bounds access, invalid free and use-after-free when processing xmc file comments
- CVE-2026-110331Abrt: abrt: incomplete cve-2026-54228/54229 fix — completeness gate bypassed via attacker-supplied count element
No corrections so far. Something wrong on this page? Report an error.