{"id":"CVE-2025-59425","aliases":["GHSA-wr9h-g72x-mwhm","PYSEC-2026-2026"],"summary":"vLLM vulnerable to timing attack at bearer auth","published_at":"2025-10-07T00:00:00Z","modified_at":"2026-09-10T03:50:30.288567Z","products":[],"rating":{"severity":"high","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false,"red_hat":"Important","vendor_ratings":[{"source":"Red Hat","rating":"Important"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.005659999791532755,"percentile":0.47756001353263855,"date":"2026-11-19T00:00:00Z"},"priority":9.5,"details":"vLLM is an inference and serving engine for large language models (LLMs). Before version 0.11.0rc2, the API key support in vLLM performs validation using a method that was vulnerable to a timing attack. API key validation uses a string comparison that takes longer the more characters the provided API key gets correct. Data analysis across many attempts could allow an attacker to determine when it finds the next correct character in the key sequence. Deployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique. Version 0.11.0rc2 fixes the issue.","affected_stack":[],"affected_other":[{"ecosystem":"CVE","package":"vllm-project/vllm","versions":["< 0.11.0rc2"],"provider":"cvelistv5","source":"CVE-2025-59425","relation":"self"},{"ecosystem":"NVD","package":"vllm:vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"fixed":["0.11.0"],"provider":"nvd","source":"CVE-2025-59425","relation":"self"},{"ecosystem":"PyPI","package":"vllm","purl":"pkg:pypi/vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"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.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.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"],"fixed":["0.11.0"],"provider":"osv","source":"GHSA-wr9h-g72x-mwhm","relation":"self"},{"ecosystem":"PyPI","package":"vllm","purl":"pkg:pypi/vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"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.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.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"],"fixed":["0.11.0"],"provider":"osv","source":"PYSEC-2026-2026","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"Red Hat AI Inference Server","cpe":"cpe:/a:redhat:ai_inference_server:3","status":"affected","packages":["rhaiis/vllm-spyre-rhel9","rhaiis/vllm-tpu-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat AI Inference Server 3.2","cpe":"cpe:/a:redhat:ai_inference_server:3.2::el9","status":"fixed","packages":["rhaiis"],"package_count":1,"fixed":[],"advisories":["RHSA-2025:23078","RHSA-2025:23079","RHSA-2025:23080","RHSA-2026:3461","RHSA-2026:3462"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI)","cpe":"cpe:/a:redhat:enterprise_linux_ai:1","status":"affected","packages":["rhelai1/bootc-amd-rhel9","rhelai1/bootc-aws-nvidia-rhel9","rhelai1/bootc-azure-amd-rhel9","rhelai1/bootc-azure-nvidia-rhel9","rhelai1/bootc-gcp-nvidia-rhel9","rhelai1/bootc-intel-rhel9","rhelai1/bootc-nvidia-rhel9","rhelai1/instructlab-amd-rhel9","rhelai1/instructlab-intel-rhel9","rhelai1/instructlab-nvidia-rhel9"],"package_count":10,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI) 3","cpe":"cpe:/a:redhat:enterprise_linux_ai:3","status":"affected","packages":["rhelai3/bootc-aws-cuda-rhel9","rhelai3/bootc-azure-cuda-rhel9","rhelai3/bootc-cuda-rhel9","rhelai3/bootc-gcp-cuda-rhel9"],"package_count":4,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-vllm-cuda-rhel9","rhoai/odh-vllm-rocm-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 2.25","cpe":"cpe:/a:redhat:openshift_ai:2.25::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3782"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 2.25","cpe":"cpe:/a:redhat:openshift_ai:2.25::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3713"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-59425"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2025-59425","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2025-59425","license":"CC-BY-4.0","published_at":"2025-10-07T14:06:49.042Z","modified_at":"2025-10-07T15:28:10.303Z","summary":"vLLM vulnerable to timing attack at bearer auth","details":"vLLM is an inference and serving engine for large language models (LLMs). Before version 0.11.0rc2, the API key support in vLLM performs validation using a method that was vulnerable to a timing attack. API key validation uses a string comparison that takes longer the more characters the provided API key gets correct. Data analysis across many attempts could allow an attacker to determine when it finds the next correct character in the key sequence. Deployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique. Version 0.11.0rc2 fixes the issue.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","source":"CVE-2025-59425"}],"affected":[{"ecosystem":"CVE","package":"vllm-project/vllm","versions":["< 0.11.0rc2"],"provider":"cvelistv5","source":"CVE-2025-59425","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/commit/ee10d7e6ff5875386c7f136ce8b5f525c8fcef48"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/releases/tag/v0.11.0"}]},{"provider":"nvd","source_id":"CVE-2025-59425","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425","severity":[],"affected":[{"ecosystem":"NVD","package":"vllm:vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"fixed":["0.11.0"],"provider":"nvd","source":"CVE-2025-59425","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"GHSA-wr9h-g72x-mwhm","relation":"self","url":"https://osv.dev/vulnerability/GHSA-wr9h-g72x-mwhm","license":"CC-BY-4.0","published_at":"2025-10-07T17:24:47Z","modified_at":"2026-09-10T03:50:30.288567Z","summary":"vLLM is vulnerable to timing attack at bearer auth","details":"### Summary\nThe API key support in vLLM performed validation using a method that was vulnerable to a timing attack. This could potentially allow an attacker to discover a valid API key using an approach more efficient than brute force.\n\n### Details\nhttps://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274\n\nAPI key validation used a string comparison that will take longer the more characters the provided API key gets correct. Data analysis across many attempts can allow an attacker to determine when it finds the next correct character in the key sequence.\n \n### Impact\nDeployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","source":"GHSA-wr9h-g72x-mwhm"}],"affected":[{"ecosystem":"PyPI","package":"vllm","purl":"pkg:pypi/vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"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.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.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"],"fixed":["0.11.0"],"provider":"osv","source":"GHSA-wr9h-g72x-mwhm","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/commit/ee10d7e6ff5875386c7f136ce8b5f525c8fcef48"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"WEB","url":"https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2026.yaml"},{"type":"PACKAGE","url":"https://github.com/vllm-project/vllm"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/releases/tag/v0.11.0"},{"type":"WEB","url":"https://pypi.org/project/vllm"}]},{"provider":"osv","source_id":"PYSEC-2026-2026","relation":"self","url":"https://osv.dev/vulnerability/PYSEC-2026-2026","license":"CC-BY-4.0","published_at":"2026-07-07T16:03:06.800906Z","modified_at":"2026-07-07T17:48:17.631626Z","summary":"vLLM is vulnerable to timing attack at bearer auth","details":"### Summary\nThe API key support in vLLM performed validation using a method that was vulnerable to a timing attack. This could potentially allow an attacker to discover a valid API key using an approach more efficient than brute force.\n\n### Details\nhttps://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274\n\nAPI key validation used a string comparison that will take longer the more characters the provided API key gets correct. Data analysis across many attempts can allow an attacker to determine when it finds the next correct character in the key sequence.\n \n### Impact\nDeployments relying on vLLM's built-in API key validation are vulnerable to authentication bypass using this technique.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","source":"PYSEC-2026-2026"}],"affected":[{"ecosystem":"PyPI","package":"vllm","purl":"pkg:pypi/vllm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"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.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.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"],"fixed":["0.11.0"],"provider":"osv","source":"PYSEC-2026-2026","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/commit/ee10d7e6ff5875386c7f136ce8b5f525c8fcef48"},{"type":"PACKAGE","url":"https://github.com/vllm-project/vllm"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/releases/tag/v0.11.0"},{"type":"PACKAGE","url":"https://pypi.org/project/vllm"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-wr9h-g72x-mwhm"}]},{"provider":"redhat-vex","source_id":"CVE-2025-59425","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2025-59425","license":"CC-BY-4.0","published_at":"2025-10-07T00:00:00Z","modified_at":"2026-03-16T08:31:17Z","summary":"vllm: Timing Attack in vLLM API Token Verification Leading to Authentication Bypass","details":"A flaw was found in vLLM’s API token authentication logic, where token comparisons were not performed in constant time. This weakness could allow an attacker to exploit timing differences to guess valid tokens and bypass authentication.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","source":"CVE-2025-59425"},{"type":"Red Hat","score":"Important","source":"CVE-2025-59425"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat AI Inference Server","cpe":"cpe:/a:redhat:ai_inference_server:3","status":"affected","packages":["rhaiis/vllm-spyre-rhel9","rhaiis/vllm-tpu-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat AI Inference Server 3.2","cpe":"cpe:/a:redhat:ai_inference_server:3.2::el9","status":"fixed","packages":["rhaiis"],"package_count":1,"fixed":[],"advisories":["RHSA-2025:23078","RHSA-2025:23079","RHSA-2025:23080","RHSA-2026:3461","RHSA-2026:3462"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI)","cpe":"cpe:/a:redhat:enterprise_linux_ai:1","status":"affected","packages":["rhelai1/bootc-amd-rhel9","rhelai1/bootc-aws-nvidia-rhel9","rhelai1/bootc-azure-amd-rhel9","rhelai1/bootc-azure-nvidia-rhel9","rhelai1/bootc-gcp-nvidia-rhel9","rhelai1/bootc-intel-rhel9","rhelai1/bootc-nvidia-rhel9","rhelai1/instructlab-amd-rhel9","rhelai1/instructlab-intel-rhel9","rhelai1/instructlab-nvidia-rhel9"],"package_count":10,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI) 3","cpe":"cpe:/a:redhat:enterprise_linux_ai:3","status":"affected","packages":["rhelai3/bootc-aws-cuda-rhel9","rhelai3/bootc-azure-cuda-rhel9","rhelai3/bootc-cuda-rhel9","rhelai3/bootc-gcp-cuda-rhel9"],"package_count":4,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-vllm-cuda-rhel9","rhoai/odh-vllm-rocm-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 2.25","cpe":"cpe:/a:redhat:openshift_ai:2.25::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3782"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 2.25","cpe":"cpe:/a:redhat:openshift_ai:2.25::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3713"],"provider":"redhat-vex","source":"CVE-2025-59425"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-59425"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-59425.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2025-59425"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2397234"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2025-59425"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/commit/ee10d7e6ff5875386c7f136ce8b5f525c8fcef48"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-wr9h-g72x-mwhm"}]}],"references":[{"type":"WEB","url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/commit/ee10d7e6ff5875386c7f136ce8b5f525c8fcef48"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/blob/4b946d693e0af15740e9ca9c0e059d5f333b1083/vllm/entrypoints/openai/api_server.py#L1270-L1274"},{"type":"WEB","url":"https://github.com/vllm-project/vllm/releases/tag/v0.11.0"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-wr9h-g72x-mwhm"},{"type":"WEB","url":"https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2026.yaml"},{"type":"PACKAGE","url":"https://github.com/vllm-project/vllm"},{"type":"WEB","url":"https://pypi.org/project/vllm"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-59425.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2025-59425"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2397234"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2025-59425"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2025-59425","url":"https://www.cve.org/CVERecord?id=CVE-2025-59425","license":"CC-BY-4.0","modified_at":"2025-10-07T15:28:10.303Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2025-59425","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59425","relation":"self"},{"provider":"osv","source_id":"GHSA-wr9h-g72x-mwhm","url":"https://osv.dev/vulnerability/GHSA-wr9h-g72x-mwhm","license":"CC-BY-4.0","modified_at":"2026-09-10T03:50:30.288567Z","relation":"self"},{"provider":"osv","source_id":"PYSEC-2026-2026","url":"https://osv.dev/vulnerability/PYSEC-2026-2026","license":"CC-BY-4.0","modified_at":"2026-07-07T17:48:17.631626Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2025-59425","url":"https://access.redhat.com/security/cve/CVE-2025-59425","license":"CC-BY-4.0","modified_at":"2026-03-16T08:31:17Z","relation":"self"}]}
