Red Hat Linux Security Advisories & CVEs
5947 advisories tracked · Red Hat Security Data API · direct feeds checked every minute; rate-limited backstops use a safe source cadence
Android app · Google Play
Monitor Red Hat 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.
Security advisories for your Red Hat release
Pick your distribution release to see every advisory issued for it and its severity mix. Fixes ship as errata — keep the system patched. This is the release's advisory history, not a per-package scan.
Official source
Red Hat Security Data API
Red Hat Enterprise Linux errata (RHSA) via the official Red Hat Security Data API — CVE severity, CVSS and affected packages. A credential-free official source.
Latest Red Hat advisories
Medium [CVE-2026-18203] Group policy extendChildren matches sibling group path prefixes
A flaw was found in the group policy evaluation logic of Keycloak, an identity and access management solution. When a group policy is set to extend permissions to child groups, the system incorrectly uses a simple text-based prefix check to verify group membership. This allows a user who belongs to a different group with a similar starting name to bypass security checks and gain unauthorized access to administrative functions or protected resources. The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires a specific group naming collision and the extendChildren policy setting to be active. Successful exploitation allows an attacker to gain unauthorized integrity-impacting permissions within the realm. The vulnerability's root cause is an improper string prefix comparison during group path validation in the authorization services. Weakness: CWE-863. Affected Red Hat products: Red Hat Build of Keycloak. Red Hat lists Red Hat Data Grid 8; Red Hat JBoss Enterprise Application Platform Expansion Pack; Red Hat Single Sign-On 7 as not affected. Red Hat does not currently list a fixing RHSA for this CVE.
Medium [CVE-2026-18211] secure-client-uris policy bypass via localhost-prefixed domains
A flaw was found in the secure-client-uris client policy executor within Keycloak core services. This component is responsible for enforcing security requirements on client configurations, such as requiring encrypted connections for redirect URIs. Due to an improper check that only looks at the start of a web address rather than properly verifying the host, an attacker can bypass these security restrictions by using a specially crafted domain name. This could allow an attacker to intercept sensitive authentication codes over unencrypted connections. The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires Dynamic Client Registration to be enabled and the attacker to control a specific localhost-prefixed domain. Successful exploitation allows an attacker to intercept authorization codes over cleartext HTTP by bypassing the secure-client-uris policy. The vulnerability's root cause is improper validation of the redirect URI host component in the secure-client-uris policy executor. Weakness: CWE-20. Affected Red Hat products: Red Hat Build of Keycloak. Red Hat lists Red Hat Data Grid 8; Red Hat JBoss Enterprise Application Platform Expansion Pack; Red Hat Single Sign-On 7 as not affected. Red Hat does not currently list a fixing RHSA for this CVE.
Medium [CVE-2026-18208] Inactive out-of-audience token introspection leaks signed JWT claim
A flaw was found in the OIDC token introspection endpoint of the keycloak-services component. Keycloak is an open-source identity and access management solution used to secure modern applications and services. The issue occurs when a confidential client, configured to receive signed JWT introspection responses, attempts to introspect a token issued for a different audience. Although the endpoint correctly identifies the token as inactive for that client, it still returns the full set of token claims within a signed JWT field. This allows an unauthorized client to bypass audience-based restrictions and access sensitive information contained in the token. The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to control a confidential client within the same realm and possess a valid token issued for a different audience. Successful exploitation allows an attacker to recover sensitive token claims that should be restricted by audience-based access controls. The vulnerability's root cause is a failure to sanitize the signed JWT field in the introspection response when a token is determined to be inactive due to an audience mismatch. Weakness: CWE-862. Affected Red Hat products: Red Hat Build of Keycloak.
Medium [CVE-2026-16105] Missing per-role authorization on RoleContainerResource composite endpoints
A flaw was found in the RoleContainerResource component of Keycloak. The issue occurs because certain name-based endpoints in the admin REST API do not properly enforce authorization checks when managing composite roles. This allows a delegated administrator with manage-realm permissions to remove essential child roles from built-in admin roles, potentially disrupting administrative functions within a realm. The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to already possess high-level delegated administrative privileges (manage-realm). Successful exploitation allows an attacker to remove child roles from built-in admin roles, leading to a loss of integrity for administrative configurations. The vulnerability's root cause is an incomplete fix for a previous issue, where authorization checks were not consistently applied to name-based REST API endpoints. Weakness: CWE-639. Affected Red Hat products: Red Hat build of Keycloak 26.6; Red Hat build of Keycloak 26.6.7. Red Hat lists Red Hat Data Grid 8; Red Hat JBoss Enterprise Application Platform Expansion Pack; Red Hat Single Sign-On 7 as not affected. Red Hat fixing advisory: RHSA-2026:68277, RHSA-2026:68278.
Medium [CVE-2026-18215] Microsoft external access-token exchange bypasses configured tenant
Keycloak provides a way to let users log in using Microsoft accounts while restricting access to a specific organization (tenant). A flaw was discovered where this restriction is ignored when using the token exchange feature. This means an attacker with a valid Microsoft token from a completely different organization could gain access to the Keycloak realm, potentially accessing sensitive data or performing unauthorized actions. The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to possess a valid Microsoft Graph access token from a different tenant. Successful exploitation allows an attacker to bypass configured tenant restrictions and gain unauthorized access to a Keycloak realm. The vulnerability's root cause is the lack of tenant ID verification during the external access-token exchange flow when interacting with the Microsoft Graph API. Weakness: CWE-287. Affected Red Hat products: Red Hat build of Keycloak 26.6; Red Hat build of Keycloak 26.6.7. Red Hat lists Red Hat Data Grid 8; Red Hat JBoss Enterprise Application Platform Expansion Pack; Red Hat Single Sign-On 7 as not affected. Red Hat fixing advisory: RHSA-2026:68277, RHSA-2026:68278.
Medium [CVE-2026-18218] Client not-before revocation ignored when realm not-before is older but nonzero
A flaw was found in the TokenManager component of the Keycloak identity management service. When an administrator attempts to revoke tokens for a specific application (client) using a "not-before" policy, the revocation may be silently ignored if the overall security realm already has an older, non-zero revocation policy in place. This issue can allow previously issued tokens to remain valid for refreshing sessions and accessing user information even after an administrator has attempted to invalidate them. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires a specific pre-existing realm configuration and the possession of valid tokens issued within a specific timeframe. Successful exploitation allows an attacker to continue using revoked tokens for refresh, introspection, and UserInfo requests. The vulnerability's root cause is a logic error in the TokenManager. NotBeforeCheck function that fails to correctly enforce client-specific revocation policies when a realm-level policy is also present. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Red Hat severity: Moderate — CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N). Weakness: CWE-862.
Medium [CVE-2026-58039] Information disclosure due to improper permission enforcement
Information disclosure due to improper permission enforcement. Red Hat rates this moderate (CVSS 4.4). Weakness: CWE-73. Red Hat lists fixing advisory RHSA-2026:48273 with package nodejs26-main-26.5.1-1.5.hum1, nodejs22-main-22.23.2-2.3.hum1, nodejs24-main-24.18.1-0.1.hum1.
Medium [CVE-2026-63362] Denial of Service via unsigned integer underflow
An unsigned integer underflow in the PubSub signature verification path in open62541 may allow a remote attacker to cause a denial of service via a crafted UDP packet. A flaw was found in open62541. This vulnerability could make the affected system unavailable to legitimate users. This Moderate severity flaw in open62541 can lead to a denial of service. The high attack complexity associated with this vulnerability reduces the likelihood of successful exploitation. This component is only present in Fedora. Red Hat does not ship this component in any core Red Hat products. Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-191.
Medium [CVE-2026-68563] Information disclosure of PostgreSQL data via insecure backup permissions
A flaw was found in ansible-collection-redhat-leapp. When a remediation task is executed with elevated privileges and the `leapp_old_postgresql_data` option is selected, a PostgreSQL data backup archive is created with insecure permissions. This allows a local non-root user on the managed node to read sensitive archived PostgreSQL data, leading to information disclosure. The vulnerability occurs when a specific Leapp remediation task, intended to back up and remove old PostgreSQL data, creates a world-readable archive in `/var/backups`. Exploitation requires local access to a managed node where this particular remediation workflow has been executed and `/var/lib/pgsql/data` existed. Red Hat severity: Moderate — CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-732. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9. Red Hat does not currently list a fixing RHSA for this CVE. Affected products named by the advisory: Red Hat package: ansible-collection-redhat-leapp.
Medium [CVE-2026-68562] Information disclosure via Leapp report tampering
A flaw was found in ansible-collection-redhat-leapp. An attacker with privileged write access to a managed node's Leapp report content can manipulate it. When an operator runs a specific remediation task, this manipulated report can cause the Ansible controller to read its own local files and copy them to the managed node. This vulnerability leads to information disclosure, potentially exposing sensitive controller-side data such as private keys or credentials. When an operator subsequently runs the `leapp_corrupted_grubenv_file` remediation, the Ansible controller may be tricked into disclosing sensitive controller-local files to the compromised managed node, crossing a trust boundary. Exploitation depends on both prior compromise of the managed node and specific operator action. Red Hat severity: Moderate — CVSS 6.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N). Weakness: CWE-610. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9. Red Hat does not currently list a fixing RHSA for this CVE. Affected products named by the advisory: Red Hat package: ansible-collection-redhat-leapp.
Medium [CVE-2026-67550] Denial of Service via out-of-bounds read
Denial of Service via out-of-bounds read. Red Hat rates this moderate (CVSS 5.7). Weakness: CWE-125.
Medium [CVE-2026-59881] Denial of Service via unnegotiated WebSocket compression
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.2, the WebSocket client accepts and decompresses frames with the RSV1 bit set even when the permessage-deflate extension was not negotiated, allowing a malicious server to cause unexpected CPU and memory consumption. This issue is fixed in version 3.14.2. A flaw was found in AIOHTTP. The WebSocket client in AIOHTTP processes compressed data frames even when the compression mechanism, known as permessage-deflate, has not been properly negotiated. A malicious server can exploit this by sending specially crafted compressed frames. This can lead to unexpected and excessive consumption of the system's central processing unit (CPU) and memory, potentially resulting in a denial of service (DoS) for legitimate users. Red Hat rates this flaw as Moderate with a CVSS score of 5.3 because exploitation requires an aiohttp WebSocket client to connect to an attacker-controlled server. In typical Red Hat product deployments, aiohttp serves as an HTTP client library for internal service communication rather than establishing WebSocket connections to untrusted endpoints. The resulting resource consumption is limited to the individual process running the affected client and does not propagate to other services or the host system. Weakness: CWE-409.
Medium [CVE-2026-12996] Denial of Service or memory leak via crafted packets
A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote authenticated peers to potentially cause a denial of service or leak memory via crafted packets during TLS session promotion or expiry A flaw was found in OpenVPN. Successful exploitation of this flaw could lead to a denial of service, making the service unavailable, or result in a memory leak, potentially exposing sensitive information. Moderate impact. While it can lead to a denial of service or memory leak, the need for prior authentication limits the attack vector, making it less severe than unauthenticated vulnerabilities. Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H). Weakness: CWE-825.
Medium [CVE-2026-11771] Denial of Service via crafted NTLM proxy response
OpenVPN version 2.1.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows attackers via an off-by-one buffer write in the NTLM proxy authentication to potentially cause a crash via a crafted NTLM response from a malicious proxy server A flaw was found in OpenVPN. A remote attacker could exploit an off-by-one buffer write vulnerability during NTLM (NT LAN Manager) proxy authentication. By sending a specially crafted NTLM response from a malicious proxy server, the attacker could cause the OpenVPN client to crash, leading to a denial of service. Exploitation requires a client to connect through a malicious NTLM proxy server, which can then send a specially crafted response. The necessity of user interaction with a compromised proxy limits the overall risk. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H). Weakness: CWE-787.
Medium [CVE-2026-13117] Denial of service or memory leakage via incomplete TLS guard
An incomplete guard in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote authenticated peers to trigger a use-after-free during TLS session promotion, potentially leading to a denial of service or memory leakage A flaw was found in OpenVPN. This can lead to a denial of service, making the service unavailable, or memory leakage, which could potentially expose sensitive information. The high attack complexity and requirement for prior authentication limit the immediate risk, but successful exploitation could disrupt VPN services or expose sensitive information. Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H). Weakness: CWE-825.
Medium [CVE-2026-60074] Date::Manip: Incorrect date parsing leads to logic errors
Date::Manip: Incorrect date parsing leads to logic errors. Red Hat rates this moderate (CVSS 4.3). Weakness: CWE-681.
Medium [CVE-2026-7260] Denial of Service via circular symbolic links in phar archives
Denial of Service via circular symbolic links in phar archives. Red Hat rates this moderate (CVSS 5.5). Weakness: CWE-606. Red Hat lists fixing advisory RHSA-2026:47200 with package php-main-8.5.9-1.hum1.
Medium [CVE-2026-18369] ACME HTTP-01 validation SSRF via IP literal identifiers and unvalidated redirects
A flaw was found in Dogtag PKI's ACME responder where the HTTP-01 challenge validator accepts IP address literals as dns identifiers and follows HTTP redirects without validating that the target is a public address. An unauthenticated ACME account holder can exploit this to perform server-side request forgery (SSRF), making the Dogtag server send HTTP GET requests to internal network services. With the InMemory database backend, the response body of internal targets is disclosed to the attacker through the ACME challenge error. Red Hat rates this Moderate because exploitation is limited to HTTP GET requests (no integrity impact), the attacker cannot read internal responses on production-supported backends (low confidentiality impact), and the ACME responder must be explicitly deployed. The Scope is Changed (S:C) because the ACME responder causes the Dogtag server to make outbound requests to services outside its own trust boundary, but the actual information gained on supported configurations is limited to network topology probing. While the SSRF is GET-only and does not directly allow data modification, administrators should be aware that internal services reachable from the Dogtag host which perform actions on HTTP GET (such as cloud instance metadata endpoints that issue temporary credentials) could be indirectly affected.
Medium [CVE-2026-56850] mTLS client identities can be reused due to HTTPS Agent connection flaw
A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. A flaw was found in Node.js. The HTTPS Agent, responsible for managing secure connections, can incorrectly reuse client identities across different requests. As a result, a client's identity, established through mutual TLS (mTLS) authentication, could be mistakenly applied to another request, potentially leading to unauthorized access or identity spoofing. This can lead to unintended identity confusion if applications are configured to use different client certificates with reused connections, potentially enabling unauthorized access within the mTLS context. Red Hat severity: Moderate — CVSS 4.1 (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N). Weakness: CWE-303. Affected Red Hat products: Red Hat Hardened Images; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9. Will not fix / out of support: Red Hat Hardened Images. Red Hat fixing advisory: RHSA-2026:48273, RHSA-2026:48305, RHSA-2026:48537. Affected products named by the advisory: Red Hat package: nodejs22; Red Hat package: nodejs24.
Medium [CVE-2026-58040] HTTPS Agent TLS session reuse skips hostname verification
HTTPS Agent TLS session reuse skips hostname verification. Red Hat rates this moderate (CVSS 6.3). Weakness: CWE-322. Red Hat lists fixing advisory RHSA-2026:48273 with package nodejs26-main-26.5.1-1.5.hum1, nodejs22-main-22.23.2-2.3.hum1, nodejs24-main-24.18.1-0.1.hum1.