High [CVE-2026-14362] HashiCorp memberlist: Denial of Service via push/pull state handling
This high-severity Red Hat Linux advisory covers CVE-2026-14362 affecting Red Hat Advanced Cluster Management for Kubernetes 2.11, Red Hat Advanced Cluster Management for Kubernetes 2.13, Red Hat Advanced Cluster Management for Kubernetes 2.14.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
HashiCorp memberlist before version 0.6.0 is vulnerable to a denial-of-service issue in its push/pull state handling that may allow an attacker with network access to the gossip port to exhaust memory on a receiving node and cause the process to terminate. This vulnerability (CVE-2026-14362) is fixed in memberlist 0.6.0.
This flaw results in a Denial of Service (DoS). Only Red Hat products that run the affected component as a live memberlist gossip agent (a process that binds and listens on a UDP/TCP gossip port for cluster membership) are exposed to this denial-of-service issue.
Products that pull in github.com/hashicorp/memberlist only as a transitive Go dependency, without starting a gossip listener, do not exercise the vulnerable push/pull state-handling code path and are not affected.
Grafana links github.com/hashicorp/memberlist solely for its optional unified-alerting high-availability (HA) clustering feature; the gossip listener only starts when unified_alerting.ha_peers (plus ha_listen_address/ha_advertise_address) is explicitly configured.
Red Hat Advanced Cluster Management for Kubernetes ships its acm-grafana component with unified alerting disabled by default (unified_alerting.enabled = false) and never sets ha_peers, so it never starts the gossip listener and does not exercise the vulnerable code path; it is not affected.
Is CVE-2026-14362 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-14362 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-14362?
Upgrade to a fixed release named by Red Hat:
- 0.6.0
- rhacm2/prometheus-alertmanager-rhel9:1787263623
- rhacm2/prometheus-alertmanager-rhel9:1787263182
- rhacm2/prometheus-alertmanager-rhel9:1786976979
- rhacm2/prometheus-alertmanager-rhel9:1786547824
- rhacm2/prometheus-alertmanager-rhel9:1786909156
- rhacm2/prometheus-alertmanager-rhel9:1787229700
- openshift4/ose-prometheus-alertmanager-rhel9:1789939284
- openshift4/ose-prometheus-alertmanager-rhel9:1788578046
- openshift4/ose-prometheus-alertmanager-rhel9:1786984418
- openshift4/ose-prometheus-alertmanager-rhel9:1787020721
- openshift4/ose-prometheus-alertmanager-rhel9:1786500210
13 more fixed releases are listed below.
Confirm against the vendor advisory before you patch.
- < 0.6.0
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 0.6.0
- rhacm2/prometheus-alertmanager-rhel9:1787263623
- rhacm2/prometheus-alertmanager-rhel9:1787263182
- rhacm2/prometheus-alertmanager-rhel9:1786976979
- rhacm2/prometheus-alertmanager-rhel9:1786547824
- rhacm2/prometheus-alertmanager-rhel9:1786909156
- rhacm2/prometheus-alertmanager-rhel9:1787229700
- openshift4/ose-prometheus-alertmanager-rhel9:1789939284
- openshift4/ose-prometheus-alertmanager-rhel9:1788578046
- openshift4/ose-prometheus-alertmanager-rhel9:1786984418
- openshift4/ose-prometheus-alertmanager-rhel9:1787020721
- openshift4/ose-prometheus-alertmanager-rhel9:1786500210
- openshift4/ose-prometheus-alertmanager-rhel9:1786584932
- RHSA-2026:60387
- RHSA-2026:60390
- RHSA-2026:60388
- RHSA-2026:54427
- RHSA-2026:57191
- RHSA-2026:60386
- RHSA-2026:70587
- RHSA-2026:65852
- RHSA-2026:57408
- RHSA-2026:57545
- RHSA-2026:54602
- RHSA-2026:54770
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Upgrade github.com/hashicorp/memberlist to version 0.6.0 or later, which fixes the push/pull state handling issue. As a temporary mitigation, restrict network access to the gossip port (UDP/TCP, commonly 7946 or 9094) to trusted cluster members only, e.g. via network policy, firewall rules, or security groups, since the flaw requires network access to the gossip listener to trigger memory exhaustion.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-46300May 13, 2026"Fragnesia" is a variant of Dirty Frag vulnerability in the ESP/XFRM leading to Local
- CVE-2026-31431Apr 22, 2026algif_aead - Revert to operating out-of-place
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.