Vulnpedia
← Search CVEs

CVE-2026-93592

HIGH 8.7

Published 2026-09-18 · Last modified 2026-09-18

vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that poisons the GPU context, causing all subsequent requests to fail until the process restarts.

ELEVATED IMPACT

Severe if exploited (CVSS 8.7), but no known exploitation and low modeled probability. Patch on a normal cadence.

Exploitation likelihood

0.5%chance of exploitation in 30 days · 45th percentile

○ In CISA KEV ○ Catalogued PoC

Impact if exploited

8.7CVSS 4.0 · HIGH

  • ConfidentialityNone
  • IntegrityNone
  • AvailabilityHigh

What an attacker needs

  • ✓Access: Reachable over the network — no local access needed
  • ✓Privileges: No account or privileges required
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable
  • ✓Requirements: No special attack requirements

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Vllm Project Vllm

Products Vllm

Weakness (CWE)

  • CWE-129: Improper Validation of Array Index

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References and research data (JSON)

Packages and version ranges

Each advisory describes its own package and affected ranges. A boundary applies to that range; it is not a universal upgrade recommendation.

  • vllm PyPI

    pkg:pypi/vllm

    ECOSYSTEM range
    • All earlier versions (introduced 0)
    • Fixed boundary (excluded): 0.28.0
    95 explicitly listed affected versions

    0.0.1, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.10.0, 0.10.1, 0.10.1.1, 0.10.2, 0.11.0, 0.11.1, 0.11.2, 0.12.0, 0.13.0, 0.14.0, 0.14.1, 0.15.0, 0.15.1, 0.16.0, 0.17.0, 0.17.1, 0.18.0, 0.18.1, 0.19.0, 0.19.1, 0.2.0, 0.2.1, 0.2.1.post1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.20.0, 0.20.1, 0.20.2, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.24.0, 0.25.0, 0.25.1, 0.26.0, 0.27.0, 0.27.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.0.post1, 0.4.1, 0.4.2, 0.4.3, 0.5.0, 0.5.0.post1, 0.5.1, 0.5.2, 0.5.3, 0.5.3.post1, 0.5.4, 0.5.5, 0.6.0, 0.6.1, 0.6.1.post1, 0.6.1.post2, 0.6.2, 0.6.3, 0.6.3.post1, 0.6.4, 0.6.4.post1, 0.6.5, 0.6.6, 0.6.6.post1, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.5.post1, 0.9.0, 0.9.0.1, 0.9.1, 0.9.2

    Additional upstream package constraints
    {
  "ecosystem": {},
  "database": {
    "source": "https://github.com/pypa/advisory-database/blob/main/vulns/vllm/PYSEC-2026-3997.yaml"
  }
}
    PyPA · PYSEC-2026-3997 · Updated 2026-09-29T09:00:03.002511196Z

Vendor product assessments

Showing 32 of 347 vendor product statements; 315 omitted. Read the full vendor advisory.

  • registry.redhat.io/rhaii/vllm-cpu-rhel9@sha256:f8a692451f509d11bf166288d614660cf8c15bab7494a822276bf458cfeb757a_amd64 as a component of Red Hat AI Inference Server 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-cpu-rhel9@sha256%3Af8a692451f509d11bf166288d614660cf8c15bab7494a822276bf458cfeb757a?arch=amd64&repository_url=registry.redhat.io/rhaii/vllm-cpu-rhel9&tag=1791857301

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:83112 Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhaii/vllm-cuda-rhel9@sha256:d8d762cc0a3bb9782fdb32ddebfb2756d79ebed8e2964ee910a9ece352afa03a_arm64 as a component of Red Hat AI Inference Server 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-cuda-rhel9@sha256%3Ad8d762cc0a3bb9782fdb32ddebfb2756d79ebed8e2964ee910a9ece352afa03a?arch=arm64&repository_url=registry.redhat.io/rhaii/vllm-cuda-rhel9&tag=1791857183

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:83120 Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhaii/vllm-spyre-rhel9@sha256:e4c4daa59819b6a5ac649a09f162e266b8690481f7487860cf39e897fe042a65_amd64 as a component of Red Hat AI Inference Server 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-spyre-rhel9@sha256%3Ae4c4daa59819b6a5ac649a09f162e266b8690481f7487860cf39e897fe042a65?arch=amd64&repository_url=registry.redhat.io/rhaii/vllm-spyre-rhel9&tag=1791858592

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:83114 Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhaii/vllm-gaudi-rhel9@sha256:ba46859d4cb085c111a27bc665c15e5f826320e86c03b940f7a28f40df79ad22_amd64 as a component of Red Hat AI Inference Server 3.5 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-gaudi-rhel9@sha256%3Aba46859d4cb085c111a27bc665c15e5f826320e86c03b940f7a28f40df79ad22?arch=amd64&repository_url=registry.redhat.io/rhaii/vllm-gaudi-rhel9&tag=1791427182

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:82061 Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-agent-rhel9@sha256:2813ff65f6c95074862dd66221b7b9b9e99430b3a5d27eba5203e107023f69e9_arm64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-agent-rhel9@sha256%3A2813ff65f6c95074862dd66221b7b9b9e99430b3a5d27eba5203e107023f69e9?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-kserve-agent-rhel9&tag=1791468381

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:51997b1a7e5e2f3c0bd76b7d23fda33902843addafcbba6333b27d5c72beb5c4_amd64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-controller-rhel9@sha256%3A51997b1a7e5e2f3c0bd76b7d23fda33902843addafcbba6333b27d5c72beb5c4?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-kserve-controller-rhel9&tag=1791468368

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:a2967b5e30b4b8c6299abde8dc0fcab8ceb15581aff94dda4f02ac6e6aa05cb7_s390x as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-controller-rhel9@sha256%3Aa2967b5e30b4b8c6299abde8dc0fcab8ceb15581aff94dda4f02ac6e6aa05cb7?arch=s390x&repository_url=registry.redhat.io/rhoai/odh-kserve-controller-rhel9&tag=1791468368

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:24cf45f8cc50e378b6a7ecb0f42568f6426242af8b2751d60350d04b3817ccd4_s390x as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-router-rhel9@sha256%3A24cf45f8cc50e378b6a7ecb0f42568f6426242af8b2751d60350d04b3817ccd4?arch=s390x&repository_url=registry.redhat.io/rhoai/odh-kserve-router-rhel9&tag=1791468401

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:96ddd9921ce58a1df83c1a89a2046651feaeb2db91e8f48740335ac7096a3457_arm64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-router-rhel9@sha256%3A96ddd9921ce58a1df83c1a89a2046651feaeb2db91e8f48740335ac7096a3457?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-kserve-router-rhel9&tag=1791468401

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9@sha256:2ab213b45e46bccd7c9287a9b402100d46d25e9e58118ae57864513de58e77ca_ppc64le as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-storage-initializer-rhel9@sha256%3A2ab213b45e46bccd7c9287a9b402100d46d25e9e58118ae57864513de58e77ca?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9&tag=1790958549

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9@sha256:856c7748eb45dbd190fb16fe90a09546ac8febf2f83e41d8068e8ac759442018_amd64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-kserve-storage-initializer-rhel9@sha256%3A856c7748eb45dbd190fb16fe90a09546ac8febf2f83e41d8068e8ac759442018?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9&tag=1790958549

    • vendor fix: For Red Hat OpenShift AI 3.4.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Vendor guidance
    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhaii/vllm-neuron-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-neuron-rhel9@sha256:1079c9afecdbc33f4790792f0d712dbf7523790a92dcfbe8fb5cf4c2d282fc5b?repository_url=registry.redhat.io/rhaii/vllm-neuron-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • no fix planned: Will not fix
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-cpu-rhel9@sha256:fb7791bbfea99e9f81529fe8cc1e7c834ca470585c27590e3d0a6834167cd436?repository_url=registry.redhat.io/rhaiis/vllm-cpu-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • no fix planned: Will not fix
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhaiis/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-cuda-rhel9@sha256:73bbc4560132c4aaa9bbd608ce9560eeae7b30bcc8f014da460afa5622139372?repository_url=registry.redhat.io/rhaiis/vllm-cuda-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhaiis/vllm-rocm-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-rocm-rhel9@sha256:37b64a8df90756aae0ee96d2f07765adbce5ed5beb2414ac3845806ad2219cfc?repository_url=registry.redhat.io/rhaiis/vllm-rocm-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhaiis/vllm-spyre-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-spyre-rhel9@sha256:3dd7eff1c62cd4609b4c76590b77bb801cd064e40642ed32b5aa900a6bc643ea?repository_url=registry.redhat.io/rhaiis/vllm-spyre-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • no fix planned: Will not fix
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhelai3/bootc-aws-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-aws-cuda-rhel9@sha256:a754d4d1126e98f203249414b3831182bb15ee6b3643452f167849defc642e4b?repository_url=registry.redhat.io/rhelai3/bootc-aws-cuda-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhelai3/bootc-azure-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-azure-rocm-rhel9@sha256:8ea1233b1fb6b82d0aa69e9e4c47d2df242001280c11a61584066c27c5bec3a5?repository_url=registry.redhat.io/rhelai3/bootc-azure-rocm-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-cuda-rhel9@sha256:b45f3bc25a7d3c9f3bfdc1de3be6db59f6c3109f62326d74fae14e832a797981?repository_url=registry.redhat.io/rhelai3/bootc-cuda-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhelai3/bootc-gcp-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-gcp-cuda-rhel9@sha256:bac5d435d156c3ddcb581d3ff05fdce9f72bd617c5b8435cede16bb17b7bf12e?repository_url=registry.redhat.io/rhelai3/bootc-gcp-cuda-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-rocm-rhel9@sha256:38ce057f97034bbb8eaea574d41cc7eebaeaa9265a4cdd966476dd3fac129c3c?repository_url=registry.redhat.io/rhelai3/bootc-rocm-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • none available: Affected
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhoai/odh-vllm-gaudi-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-vllm-gaudi-rhel9@sha256:87eec3862eb6ddef445f89dcf6fd89add7ef202ea7c563b1ee7347537fb3e250?repository_url=registry.redhat.io/rhoai/odh-vllm-gaudi-rhel9

    • workaround: Restrict access to the inference service or filter requests at an upstream reverse proxy or API gateway: 1. Limit network access: Deploy firewall rules or OpenShift NetworkPolicies so that the inference server ports and endpoints are accessible only by authenticated, trusted internal clients. 2. Ingress request validation: Configure an API gateway or reverse proxy placed in front of the model server to inspect request payloads for the `/v1/embeddings` and `/pooling` endpoints, rejecting requests where the `input` array contains negative numbers, or restricting untrusted clients to submitting text prompt strings rather than raw token lists. Caveats: Inspecting request bodies at an intermediary gateway layer may introduce slight processing latency. Modifying reverse proxy rules or applying network policies may require a service configuration reload or restart, which can temporarily disrupt in-flight connections.
    • no fix planned: Will not fix
    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9@sha256:1edfd89a924a83901845cd773012a3aeca70c09a2175a87e83351140efc80485_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-ai-gateway-payload-processing-rhel9@sha256%3A1edfd89a924a83901845cd773012a3aeca70c09a2175a87e83351140efc80485?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9&tag=1791860396

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-eval-hub-rhel9@sha256:cb8f1ce5d2c2ae7a10d841837c7b18d3856f66869fc45d7bc8b4b193a4edbca8_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-eval-hub-rhel9@sha256%3Acb8f1ce5d2c2ae7a10d841837c7b18d3856f66869fc45d7bc8b4b193a4edbca8?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-eval-hub-rhel9&tag=1791852583

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-llama-stack-core-rhel9@sha256:0aa47e4978f9ff14ca7e1341d4b26621cb8c271f0dff6fc8324c72afa5dbd17b_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-llama-stack-core-rhel9@sha256%3A0aa47e4978f9ff14ca7e1341d4b26621cb8c271f0dff6fc8324c72afa5dbd17b?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-llama-stack-core-rhel9&tag=1790958470

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-maas-controller-rhel9@sha256:e305c12082dbed64798cc8ce855362f5703559f141308a7a0523f94d13886107_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-maas-controller-rhel9@sha256%3Ae305c12082dbed64798cc8ce855362f5703559f141308a7a0523f94d13886107?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-maas-controller-rhel9&tag=1791790095

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-mod-arch-autorag-rhel9@sha256:72b8f8d8a63c0664a729ec7afbfaa3e9ddb41d299253ed110b7358a91f55d144_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-mod-arch-autorag-rhel9@sha256%3A72b8f8d8a63c0664a729ec7afbfaa3e9ddb41d299253ed110b7358a91f55d144?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-mod-arch-autorag-rhel9&tag=1791860994

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-model-performance-data-rhel9@sha256:4ce3053cb04fdcdb6e2dfc5ba8f51cbd78d0d32c83f9e66ce376d273a592080f_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-model-performance-data-rhel9@sha256%3A4ce3053cb04fdcdb6e2dfc5ba8f51cbd78d0d32c83f9e66ce376d273a592080f?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-model-performance-data-rhel9&tag=1790958081

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-pipeline-runtime-minimal-cpu-py312-rhel9@sha256:a320d0547d3267d7ce0a3e004a44aed47d91b885ffe9840a65715e32a08ae0ec_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-pipeline-runtime-minimal-cpu-py312-rhel9@sha256%3Aa320d0547d3267d7ce0a3e004a44aed47d91b885ffe9840a65715e32a08ae0ec?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-pipeline-runtime-minimal-cpu-py312-rhel9&tag=1791829069

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-th06-cuda130-torch210-py312-rhel9@sha256:7e0fb9bebdad1ebdef398243022fbfb29f6bd5673c00c4635745e0a92545ab60_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-th06-cuda130-torch210-py312-rhel9@sha256%3A7e0fb9bebdad1ebdef398243022fbfb29f6bd5673c00c4635745e0a92545ab60?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-th06-cuda130-torch210-py312-rhel9&tag=1791961113

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • registry.redhat.io/rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9@sha256:7b75fd02b3628b485fa58e89db548116c941941ec5da885767357e752bd03dd5_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-trustyai-vllm-orchestrator-gateway-rhel9@sha256%3A7b75fd02b3628b485fa58e89db548116c941941ec5da885767357e752bd03dd5?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9&tag=1791363252

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00
  • rhoai/odh-th-torch-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not in execute path

    pkg:oci/odh-th-torch-cuda-py312-rhel9@sha256:efd7b3607b699092c68359d20ef0d0043114191a097637667c0d2cf78fbea702?repository_url=registry.redhat.io/rhoai/odh-th-torch-cuda-py312-rhel9

    Red Hat · CVE-2026-93592 · Updated 2026-10-19T11:31:30+00:00

Known Affected Software Configurations

VendorProductVersion range
VllmVllm< 0.28.0

All CVSS metrics

  • HIGH 8.7 v4.0 · CNA Primary
    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • HIGH 7.5 v3.1 · CNA Primary
    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
  • HIGH 8.7 v4.0 · NVD Secondary
    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
  • HIGH 7.5 v3.1 · NVD Secondary
    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

Exploit-tagged references (not proof of a PoC)

Advisories

Technical & other

Sources: NVD · CVE.org · EPSS