Nir Ohfeld

A critical vulnerability (CVE-2025-23266), dubbed “NVIDIAScape”, exists in the NVIDIA Container Toolkit and GPU Operator. This vulnerability allows attackers to escape containers and potentially gain root access on the host system. The flaw is due to a misconfiguration related to the handling of Open Container Initiative (OCI) hooks. Exploitation can be achieved with a simple three-line Dockerfile. Approximately 37% of cloud services are estimated to be affected. Successful exploitation could lead to privilege escalation, information disclosure, data tampering, and denial of service.

A security issue exists in ingress-nginx where the `mirror-target` and `mirror-host` Ingress annotations can be exploited to inject arbitrary configuration into nginx. Successful exploitation can lead to arbitrary code execution within the context of the ingress-nginx controller and potential disclosure of Secrets accessible to the controller. In a default installation, the controller has access to all Secrets cluster-wide. The issue stems from unsanitized mirror annotations.

A security issue exists where the `auth-tls-match-cn` Ingress annotation can be used to inject configuration into nginx. This may allow a remote attacker to execute arbitrary code within the context of the ingress-nginx controller and disclose Secrets accessible to the controller. In default installations, the controller typically has access to all Secrets cluster-wide.

A security issue exists in the ingress-nginx controller due to insufficient input validation and inadequate spatial separation. An unauthenticated attacker with network access to the pod network can send a specially crafted request to the admission webhook endpoint on port 8443. This allows the attacker to inject malicious NGINX configurations and achieve arbitrary code execution in the context of the controller. Successful exploitation can lead to the disclosure of Kubernetes Secrets accessible to the controller, which, in default installations, may include all Secrets cluster-wide, potentially granting full control over the Kubernetes cluster.

A security issue was discovered in ingress-nginx where attacker-provided data are included in a filename by the ingress-nginx Admission Controller feature, resulting in directory traversal within the container. This could result in denial of service, or when combined with other vulnerabilities, limited disclosure of Secret objects from the cluster. The issue affects over 6,500 clusters and could lead to unauthenticated remote code execution (RCE) or secret theft.

A security issue exists in ingress-nginx where the `auth-url` Ingress annotation can be exploited to inject configuration into nginx. Successful exploitation can lead to arbitrary code execution within the context of the ingress-nginx controller and potential disclosure of Secrets accessible to the controller. In a default installation, the controller has access to all Secrets within the cluster. The issue is due to insufficient input validation.

The issue is related to insufficient access controls in the Open Management Infrastructure (OMI) extensions for managing Azure virtual machines, allowing an attacker to elevate their privileges.

The issue is related to an elevation of privilege vulnerability in Open Management Infrastructure (OMI). It is associated with inadequate access controls in OMI extensions for managing Azure virtual machines. Exploitation of this issue may allow an attacker to elevate their privileges.

The issue is related to an elevation of privilege vulnerability in Open Management Infrastructure (OMI), which is associated with inadequate access control. This vulnerability can be exploited to allow an attacker to escalate their privileges. The estimated number of potentially affected devices worldwide is not available. There is no information about real-world incidents where this issue was exploited.

The issue is related to a remote code execution vulnerability in the Open Management Infrastructure (OMI) agent, which is installed by default in Linux environments on Microsoft Azure. This vulnerability, also known as OMIGOD, allows an attacker to execute arbitrary code with root privileges. The problem is present in the OMI Agent application, which is installed without the user's knowledge. The estimated number of potentially affected devices worldwide is not specified, but it is mentioned that the vulnerability affects countless Azure customers. There is no information about real-world incidents where this issue was exploited.