Ronen Shustin

**Name of the Vulnerable Software and Affected Versions** Azure Entra ID (affected versions not specified) **Description** An issue exists in Azure Entra ID where external initialization of trusted variables or data stores can allow an unauthorized attacker to elevate privileges locally. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Triton Inference Server versions prior to 25.07 **Description** NVIDIA Triton Inference Server for Windows and Linux contains a vulnerability in the Python backend that allows an attacker to cause an out-of-bounds write by sending a specially crafted request. Successful exploitation of this vulnerability may lead to remote code execution, denial of service, data tampering, or information disclosure. The vulnerability chain allows unauthenticated attackers to gain full control of the server. **Recommendations** Upgrade to version 25.07 or higher.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Triton Inference Server versions (affected versions not specified) **Description** NVIDIA Triton Inference Server for Windows and Linux contains an issue in the Python backend where an attacker could cause an out-of-bounds read by sending a request. A successful exploit of this issue might lead to information disclosure. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ingress-nginx versions prior to v1.11.5 ingress-nginx versions v1.12.0-beta.0 through v1.12.1 **Description** 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. **Recommendations** Upgrade to ingress-nginx version 1.11.5 or later. Upgrade to ingress-nginx version 1.12.1 or later.

**Name of the Vulnerable Software and Affected Versions** ingress-nginx versions prior to 1.11.5 ingress-nginx versions 1.12.0-beta.0 through 1.12.0 **Description** 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. **Recommendations** Update to version 1.11.5 or later. Update to version 1.12.1 or later. As a temporary workaround, restrict or avoid using the `auth-tls-match-cn` annotation.

**Name of the Vulnerable Software and Affected Versions** Ingress-nginx versions prior to 1.12.1, from 1.12.0-beta.0 before 1.12.1 **Description** Ingress-nginx is vulnerable to a critical remote code execution (RCE) vulnerability (CVE-2025-1974) with a CVSS score of 9.8. This flaw allows unauthenticated attackers with access to the pod network to execute arbitrary code within the ingress-nginx controller. Successful exploitation could lead to full cluster takeover and exposure of sensitive secrets. The vulnerability stems from improper isolation or compartmentalization within the controller. A proof-of-concept (PoC) exploit is publicly available. This vulnerability is actively being exploited. The Admission Controller, listening on port 8443, is a key component affected by this issue. **Recommendations** Upgrade Ingress-nginx to version 1.12.1 or later. Restrict network access to the Admission Controller, specifically port 8443. Implement network segmentation, strong authentication, and authorization policies for services on port 8443. Regularly audit and patch vulnerabilities. Remove any server-snippet annotations from your ingress configurations.

**Name of the Vulnerable Software and Affected Versions** ingress-nginx versions prior to v1.12.1 ingress-nginx versions before v1.11.5 ingress-nginx versions from v1.12.0-beta.0 before v1.12.1 **Description** 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. **Recommendations** For versions prior to v1.12.1, update to v1.12.1 or later to fix the vulnerability. For versions before v1.11.5, update to v1.11.5 or later to fix the vulnerability. For versions from v1.12.0-beta.0 before v1.12.1, update to v1.12.1 or later to fix the vulnerability. As a temporary workaround, consider restricting admission controller access until a patch is available.

**Name of the Vulnerable Software and Affected Versions** ingress-nginx versions prior to v1.11.5 ingress-nginx versions from v1.12.0-beta.0 through v1.12.1 **Description** 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. **Recommendations** Update to a version of ingress-nginx greater than or equal to v1.11.5. Update to a version of ingress-nginx greater than or equal to v1.12.1.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit versions up to and including 1.17.3 NVIDIA GPU Operator versions up to and including 24.9.1 **Description** NVIDIA Container Toolkit and NVIDIA GPU Operator are affected by a Time-of-Check Time-of-Use (TOCTOU) vulnerability. This flaw can allow a crafted container image to gain access to the host file system, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. A bypass was discovered for a previously patched security flaw, reflagged as CVE-2025-23359. The vulnerability exists due to errors in synchronization when using a shared resource, creating a race condition. **Recommendations** NVIDIA Container Toolkit versions up to and including 1.17.3: Upgrade to a newer version to address the vulnerability. NVIDIA GPU Operator versions up to and including 24.9.1: Upgrade to a newer version to address the vulnerability.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit versions are affected, but specific versions are not provided in the input data. **Description** The issue is related to an improper isolation vulnerability where a specially crafted container image could lead to modification of a host binary. A successful exploit may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The "GET /api/v1/status/{job id}" and "POST /api/v1/search" API endpoints are mentioned, with the `job id` variable and `Content-Type` being relevant. No information is provided about the estimated number of potentially affected devices or real-world incidents. **Recommendations** Since specific affected versions of NVIDIA Container Toolkit are not provided, a general recommendation based on the available data is to apply the latest security update released by NVIDIA for its Container Toolkit and GPU Operator to address the critical vulnerabilities.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit (affected versions not specified) **Description** The NVIDIA Container Toolkit contains an improper isolation vulnerability. A specially crafted container image could lead to untrusted code running in the host’s network namespace. This issue is present only when the NVIDIA Container Toolkit is configured in a nondefault way. A successful exploit may lead to denial of service and escalation of privileges. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit (affected versions not specified) **Description** The NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to untrusted code obtaining read and write access to host devices. This issue is present only when the NVIDIA Container Toolkit is configured in a nondefault way. A successful exploit may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit versions prior to the fixed version NVIDIA GPU Operator versions prior to the fixed version **Description** The issue is related to errors in processing symbolic links, which can be exploited by a remote attacker to impact data integrity. A specially crafted container image can lead to the creation of unauthorized files on the host, although the name and location of these files cannot be controlled by the attacker. This might result in data tampering. **Recommendations** For NVIDIA Container Toolkit versions prior to the fixed version, update to the latest version as outlined in the remediation guide. For NVIDIA GPU Operator versions prior to the fixed version, update to the latest version as outlined in the remediation guide. As a temporary workaround, consider restricting access to the vulnerable components until a patch is available. Review security configurations to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** NVIDIA Container Toolkit versions 1.16.1 or earlier **Description** The issue is related to the default mode of operation in NVIDIA Container Toolkit, allowing a specially crafted container image to create empty files on the host file system. This vulnerability does not impact use cases where CDI is used. A successful exploit may lead to data tampering. The vulnerability is also associated with a null pointer dereference due to concurrent access to a resource, potentially allowing a remote attacker to modify arbitrary data by using a specially crafted container image. **Recommendations** For NVIDIA Container Toolkit versions 1.16.1 or earlier, consider updating to a version that contains a fix for this issue, as no specific workaround is provided in the given information. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Defender for IoT (affected versions not specified) **Description** The issue is related to incorrect code generation management in Microsoft Defender for IoT, which can be exploited by a remote attacker to execute arbitrary code using a specially crafted request. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Defender for IoT (affected versions not specified) **Description** The issue is related to insufficient access control in Microsoft Defender for IoT, which can be exploited to elevate privileges in the system. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Defender for IoT (affected versions not specified) **Description** The issue is related to incorrect code generation management in Microsoft Defender for IoT, which can be exploited by a remote attacker to execute arbitrary code using a specially crafted request. This may also involve an SQL injection vulnerability in the update-handshake endpoint, potentially allowing authentication bypass. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Defender for IoT (affected versions not specified) **Description** The issue is related to a lack of protection measures for the SQL query structure in Microsoft Defender for IoT, which can be exploited to execute arbitrary code. This can potentially allow an attacker to bypass authentication. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** RCDCAP versions prior to 1.0.5 **Description** The issue allows remote attackers to execute arbitrary code or cause a denial of service, resulting in memory corruption and application crash, via specially crafted packets. **Recommendations** For versions prior to 1.0.5, update to version 1.0.5 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Microsoft Azure Stack (affected versions not specified) **Description** The issue is related to a spoofing vulnerability that allows an attacker to bypass authentication. This can be exploited by a remote attacker using a specially crafted request, potentially leading to spoofing attacks. The vulnerability exists due to Azure Stack's failure to properly validate certain requests. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.