See how red hat compares to other vendors in security performance
A flaw was found in the OpenShift Pipelines operator (tektoncd/operator). The operator ships a ClusterRoleBinding (tekton-scheduler-rolebinding) that binds ClusterRole/tekton-scheduler-role to the system:authenticated group, granting all authenticated users cluster-wide create/update/patch/delete permissions on kueue.x-k8s.io resources (ResourceFlavor, Workload, WorkloadPriorityClass) and create/update permissions on cert-manager.io resources (Certificate, Issuer). When Kueue CRDs are present (e.g., via RHOAI), any authenticated user can disrupt cross-tenant workload scheduling by deleting ResourceFlavors, destroy other tenants' Workload objects, or tamper with scheduling priority. When cert-manager is installed, any authenticated user can create Certificate objects targeting arbitrary Secrets, including the default ingress controller's TLS Secret (openshift-ingress/router-certs-default), causing cert-manager to overwrite it with an attacker-influenced certificate. This confused deputy attack crosses authorization boundaries ā the attacker cannot write Secrets directly but leverages cert-manager's ServiceAccount to do so. The RBAC objects are installed unconditionally even when the Tekton Scheduler feature is disabled.
A vulnerability in the assisted-service REST API, an optional Assisted Installer (assisted-service) component in the Multicluster Engine (MCE), allows an authenticated user with minimal namespace-scoped privileges to obtain administrative credentials for arbitrary clusters provisioned through the hub.
The credentials download endpoint (GET /v2/clusters/{clusterid}/credentials, which returns the kubeadmin password) and the kubeconfig download endpoint are operational in AUTHTYPE=local mode, the only authentication mode available in on-premises ACM/MCE hub deployments. The local authenticator unconditionally grants full administrative access to any request bearing a valid JWT, with no per-endpoint restrictions. A valid local JWT is embedded as a plaintext query parameter in InfraEnvStatus.ISODownloadURL and is readable by any user who has get rights on an InfraEnv object in their own namespace.
The affected components ship as part of Multicluster Engine (MCE). The Red Hat Advanced Cluster Management (ACM) deployments that include MCE are equally affected. This issue does not affect the hosted SaaS offering (console.redhat.com), which uses a different authentication mode.
Successful exploitation gives the attacker the kubeadmin password and kubeconfig for any OpenShift cluster provisioned through the affected hub, granting unrestricted root-level administrative access to those spoke clusters.
A heap-based buffer overflow was found in Corosync's Totem Process Group (totempg) message reassembly. When processing fragmented multicast messages, the buffer used to reassemble fragments lacks a runtime bounds check in release builds. A network-adjacent attacker able to send crafted multicast protocol messages to the cluster could cause a heap buffer overflow with attacker-controlled data. This can crash the Corosync daemon, causing a denial of service to the entire cluster, and may potentially allow further exploitation given sufficient heap-corruption control.
A flaw was found in EAP's IIOP. The listener's NameService would accept bind operations without authentication, allowing an attacker to hijack JNDI lookups and binding them to a malicious ORB, achieving MITM or DoS on further invocations.
A flaw was found in RESTEasy's SourceProvider. This vulnerability allows an unauthenticated attacker to perform an unauthenticated remote file read. By sending a specially crafted XML body with a DOCTYPE declaration referencing external entities to an endpoint that accepts application/xml and returns Source or StreamSource, the server can be tricked into resolving the entity and including sensitive file contents in the HTTP response. This is due to the SourceProvider.writeTo() method creating a SAXParser without disabling external entity resolution, leading to an XML External Entity (XXE) vulnerability.
Important: kernel-rt security, bug fix, and enhancement update
Important: kernel security, bug fix, and enhancement update
A flaw was found in Keycloak. When the logging format is configured to a verbose, user-supplied pattern (such as the pre-defined 'long' pattern), sensitive headers including Authorization and Cookie are disclosed to the logs in cleartext. An attacker with read access to the log files can extract these credentials (e.g., bearer tokens, session cookies) and use them to impersonate users, leading to a full account compromise.
A flaw was found in rpm. A local attacker could supply a specially crafted .gem filename containing RPM macro syntax. When a user or automated workflow invokes rpmuncompress -x on this file, the macro expansion occurs during command construction. This allows the attacker to execute arbitrary commands with the privileges of the invoking account, leading to a compromise of confidentiality, integrity, and availability.
A flaw was found in Red Hat Quay's repository-level mirror configuration feature. The POST and PUT handlers in endpoints/api/mirror.py accept an externalreference parameter without SSRF validation, unlike the organization-level mirror handlers which apply validateexternalregistryurl(). A repository administrator can supply a crafted hostname that causes the Quay mirror worker to make requests via Skopeo to internal network services, cloud metadata endpoints, or other resources not intended to be reachable from the Quay application.
General availability of the satellite/iop-host-inventory-frontend-rhel9 container image
Technical preview of the satellite/iop-vmaas-rhel9 container image
General availability of the satellite/iop-remediations-rhel9 container image
original reporting:
Missing Authentication ā pre-auth CosNaming write ops on iiop-openjdk :3528 (JBoss EAP)
Missing authentication on the IIOP CosNaming service: the :3528 IIOP listener's NameService accepts bind/rebind/unbind operations without any authentication, allowing an unauthenticated attacker to hijack EJB JNDI lookups by rebinding stub references to an attacker-controlled ORB (MITM for all subsequent client invocations) or to unbind critical services for denial of service. findings/jboss-eap96.md
General availability of the satellite/iop-remediations-rhel9 container image
General availability of the satellite/iop-host-inventory-frontend-rhel9 container image
Technical preview of the satellite/iop-vmaas-rhel9 container image
satellite/iop-vulnerability-engine-rhel9 container image available as a Technology Preview
satellite/iop-vulnerability-engine-rhel9 container image available as a Technology Preview
Important: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 update is now available (RHBQ 3.33.3.SP1)
A flaw was found in rpm. An attacker can exploit a command injection vulnerability by influencing the path or filename of a tarball processed by rpmbuild -t to include shell metacharacters. This is particularly relevant in automated build or continuous integration (CI) workflows that ingest externally supplied artifact names. Successful exploitation allows for arbitrary command execution with the privileges of the build user, which could lead to information disclosure or disruption of the build environment.
A flaw was found in rpmuncompress. This command injection vulnerability allows a local attacker to execute arbitrary commands. This occurs when rpmuncompress processes a specially crafted archive filename containing shell metacharacters, which are not properly escaped before being passed to shell command strings. Successful exploitation requires user interaction, where a user or automated workflow invokes rpmuncompress on the malicious file, leading to high impact on the confidentiality, integrity, and availability of data accessible to the invoking user.
A flaw was found in the OpenShift Console, an endpoint for plugins to serve resources in multiple languages: /locales/resources.json. This endpoint's lng and ns parameters are used to construct a filepath in pkg/plugins/handlers unsafely.go#L112 Because of this unsafe filepath construction, an authenticated user can manipulate the path to retrieve any JSON files on the console's pod by using sequences of ../ and valid directory paths.
A flaw was found in the OpenShift Console Dev Console webhook helper endpoints. The /api/dev-console/webhooks/github, /gitlab, and /bitbucket endpoints accept user-supplied hostName/baseURL parameters and perform server-side HTTP POST requests from the openshift-console pod to arbitrary URLs without URL validation or private-range blocking. By appending a query separator (?) to the hostName, the attacker neutralizes the fixed URL suffix and gains full path control, making this a general-purpose authenticated HTTP POST proxy. The full target response (status code, headers, and body) is reflected back to the caller without size limits. Any authenticated console user, including those with no project access, can exploit this to reach cluster-internal HTTP services from the console pod network position with arbitrary POST bodies and attacker-specified headers. The header denylist uses case-sensitive exact matching, allowing bypass of Cookie and X-CSRFToken filtering via case variants. No HTTP client timeout or response body size limit is enforced.
A flaw was found in the OpenShift Console Helm catalog proxy. A tenant with namespace edit permissions can create a ProjectHelmChartRepository (PHCR) resource with an arbitrary spec.connectionConfig.url. When any user browses the namespace Helm catalog, the openshift-console pod fetches that URL server-side without URL validation or private-range blocking. The tenant can supply custom CA certificates, TLS client certificates, and basic authentication credentials from namespace-scoped ConfigMaps and Secrets that the console pod consumes for the outbound request, enabling the console to present attacker-controlled authentication identities. The console pod fetch bypasses tenant namespace egress NetworkPolicy restrictions. Tenant-controlled chart metadata with trust-spoofed annotations is preserved in the aggregated catalog response visible to other users. Additionally, if a cluster-admin installs a tenant-planted chart through the console UI, cluster-scoped resources (ClusterRole, ClusterRoleBinding) are created under admin authority, enabling admin-mediated privilege escalation. Same-namespace Helm catalog availability can be degraded by planting multiple slow-responding PHCRs.
A path traversal flaw was found in SSSD's AD GPO provider. The adgpoextractsmbcomponents() function does not sanitize .. sequences in the gPCFileSysPath LDAP attribute, allowing an attacker with AD GPO management access to write files outside the GPO cache directory as root. On default RHEL configurations with SELinux enforcing, this can be used to inject Kerberos configuration leading to authentication bypass.