Vulnerabilidades de Red Hat Red Hat Enterprise Linux AI (RHEL AI) (CVE)

Registros CVE publicados para Red Hat Red Hat Enterprise Linux AI (RHEL AI), los más recientes primero. Siga el producto para recibir un correo con cada nueva.

5 resultados
7.1Alta
CVE-2025-6242

Vllm: server side request forgery (ssrf) in mediaconnector

Red Hat Red Hat AI Inference Server; Red Hat Red Hat Enterprise Linux AI (RHEL AI)

A Server-Side Request Forgery (SSRF) vulnerability exists in the MediaConnector class within the vLLM project's multimodal feature set. The load_from_url and load_from_url_async methods fetch and process media from user-provided URLs without adequate restrict…

5.5Media
CVE-2024-11079

Ansible-core: unsafe tagging bypass via hostvars object in ansible-core

ansible-core; Red Hat Ansible Automation Platform Execution Environments; Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8; Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9

A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs a…

6.2Media
CVE-2024-8939

Vllm: denials of service in vllm json web api

vllm; Red Hat Red Hat Enterprise Linux AI (RHEL AI)

A vulnerability was found in the ilab model serve component, where improper handling of the best_of parameter in the vllm JSON web API can lead to a Denial of Service (DoS). The API used for LLM-based sentence or chat completion accepts a best_of parameter to…

5.5Media
CVE-2024-8775

Ansible-core: exposure of sensitive information in ansible vault files due to improper logging

ansible-core; Red Hat Ansible Automation Platform Execution Environments; Red Hat Discovery 1 for RHEL 9; Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 8

A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true…