Skip to content
CVE-2026-127029: High-Risk Denial of Service Vulnerability in Red Hat

CVE-2026-127029: High-Risk Denial of Service Vulnerability in Red Hat

First seen 13 Nov 2026, 07:11 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 13, 2026 at 07:12 UTC

CVE-2026-127029, published on November 12, 2026, identifies a high-risk vulnerability in Red Hat Enterprise Linux that affects FreeRADIUS deployments with EAP-SIM authentication enabled. An unauthenticated remote attacker can exploit this flaw to cause a denial of service by crashing the RADIUS server without needing valid credentials. Organizations using FreeRADIUS with EAP-SIM enabled and exposed to untrusted networks are particularly vulnerable. The attack involves sending malformed EAP-SIM authentication traffic, leading to potential service disruptions for wired, wireless, or VPN access. Immediate exploitation status remains uncertain as no proof-of-concept or active exploitation has been confirmed. Administrators are advised to disable the EAP-SIM module if not in use and restrict RADIUS traffic to trusted IP addresses. Monitoring for unusual RADIUS traffic and service interruptions is recommended.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-12
CVE-2026-127029 published
Red Hat disclosed a high-risk vulnerability allowing denial of service via FreeRADIUS with EAP-SIM enabled.
access.redhat.com

More articles in this cluster (4)

Following this threat?

Track CVE-2026-127029 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Who is affected by CVE-2026-127029?
Organizations running FreeRADIUS with EAP-SIM enabled and exposed to untrusted networks are affected.
What actions should I take to mitigate this vulnerability?
Disable the EAP-SIM module if not required and restrict RADIUS traffic to trusted IP addresses.
Is there any active exploitation of this vulnerability?
Currently, there is no confirmed active exploitation or proof-of-concept code available.