{"answers":{"affected":"3 open source packages ship an affected version, including mlflow.","exploited":"There is no known exploitation of CVE-2026-71211 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-71211 is a high-severity server-side request forgery vulnerability in mlflow, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71211 and fix it if it is affected.\n\nWhat it is: CVE-2026-71211 is a high-severity server-side request forgery vulnerability in mlflow, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71211 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed\n- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed\n- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed\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-2026-71211/ (Markdown: https://insights.sbomify.com/CVE-2026-71211/index.md)","id":"CVE-2026-71211","markdown":"https://insights.sbomify.com/CVE-2026-71211/index.md","name":"CVE-2026-71211","record":{"aliases":["GHSA-h7x2-h6g9-p789","MINI-wr6r-7322-h4q6","PYSEC-2026-3865"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow AI Gateway","requires_auth":"low_privilege","summary":"Attackers can exploit unvalidated API base URLs in MLflow's AI Gateway to perform Server-Side Request Forgery, accessing internal resources via the proxy endpoint.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TuranSec","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"MLflow's AI Gateway accepts an auth_config.api_base value when creating a gateway secret (mlflow/server/handlers.py, _create_gateway_secret) with no validation of scheme, host, or IP range; the value is stored verbatim. The gateway proxy endpoint (mlflow/server/gateway_api.py, raw_proxy) subsequently issues an HTTP request to that stored api_base plus a caller-supplied path and returns the full response body.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-08-05","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-05T20:25:34Z","kind":"github_poc","ref":"https://github.com/Abdivasiyev2008/CVE-2026-71211-exploit","stars":0,"title":"CVE-2026-71211 exploit"}],"tier":"poc_unverified"},"has_fix":true,"headline":"mlflow - Unvalidated Gateway Secret api_base Enables SSRF via Gateway Proxy Endpoint","id":"CVE-2026-71211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"xidown - Argument Injection via Unterminated yt-dlp Command Line Construction","id":"CVE-2026-71212"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["3.13.0"],"last_affected":["3.15.2"],"package":"mlflow","purl":null,"source":"GHSA-h7x2-h6g9-p789"},{"ecosystem":"PyPI","fixed":[],"introduced":["3.13.0"],"last_affected":["3.15.2"],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-h7x2-h6g9-p789"},{"ecosystem":"PyPI","fixed":[],"introduced":["3.13.0"],"last_affected":["3.15.2"],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-3865"}],"prev":{"headline":"mealie - DNS-Rebinding TOCTOU in SSRF Guard Allows Internal Network and Cloud Metadata Access","id":"CVE-2026-71210"},"products":["mlflow"],"published":"2026-08-05","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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["mlflow"]},"summary":"Attackers can exploit unvalidated API base URLs in MLflow's AI Gateway to perform Server-Side Request Forgery, accessing internal resources via the proxy endpoint.","url":"https://insights.sbomify.com/CVE-2026-71211/"}