{"answers":{"affected":"2 open source packages ship an affected version, including @portkey-ai/gateway. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-66405 in the wild and no public exploit code.","fix":"Upgrade @portkey-ai/gateway to 1.14.0 or later.","what":"CVE-2025-66405 is a medium-severity server-side request forgery vulnerability in Portkey-AI gateway, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66405 and fix it if it is affected.\n\nWhat it is: CVE-2025-66405 is a medium-severity server-side request forgery vulnerability in Portkey-AI gateway, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-66405 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @portkey-ai/gateway (npm): affected all versions; fixed in 1.14.0\n- @portkey-ai/gateway (npm): affected all versions; fixed in 1.14.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-66405/ (Markdown: https://insights.sbomify.com/CVE-2025-66405/index.md)","id":"CVE-2025-66405","markdown":"https://insights.sbomify.com/CVE-2025-66405/index.md","name":"CVE-2025-66405","record":{"aliases":["GHSA-hhh5-2cvx-vmfp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI Gateway","requires_auth":"none","summary":"Attackers can exploit a custom host header to force the AI Gateway to perform unauthorized external requests, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gateway","vendor":"portkey"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Portkey.ai Gateway is a blazing fast AI Gateway with integrated guardrails. Prior to 1.14.0, the gateway determined the destination baseURL by prioritizing the value in the x-portkey-custom-host request header. The proxy route then appends the client-specified path to perform an external fetch. This can be maliciously used by users for SSRF attacks. This vulnerability is fixed in 1.14.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Portkey.ai Gateway: Server-Side Request Forgery (SSRF) in Custom Host","id":"CVE-2025-66405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Improper Authorization Check for SSH Certificate Revocation","id":"CVE-2025-66406"},"packages":[{"ecosystem":"npm","fixed":["1.14.0"],"introduced":["0"],"last_affected":[],"package":"@portkey-ai/gateway","purl":null,"source":"GHSA-hhh5-2cvx-vmfp"},{"ecosystem":"npm","fixed":["1.14.0"],"introduced":["0"],"last_affected":[],"package":"@portkey-ai/gateway","purl":"pkg:npm/%40portkey-ai/gateway","source":"GHSA-hhh5-2cvx-vmfp"}],"prev":{"headline":"mcp-server-kubernetes potential security issue in exec_in_pod tool","id":"CVE-2025-66404"},"products":["gateway"],"published":"2025-12-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-02","vendors":["Portkey-AI"]},"summary":"Attackers can exploit a custom host header to force the AI Gateway to perform unauthorized external requests, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2025-66405/"}