{"answers":{"affected":"3 open source packages ship an affected version, including sglang. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7302 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7302 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7302 is a critical path traversal vulnerability in SGLang, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7302 and fix it if it is affected.\n\nWhat it is: CVE-2026-7302 is a critical path traversal vulnerability in SGLang, published on 18 May 2026. 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-2026-7302 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sglang (PyPI): affected from 0.5.5 up to 0.5.12; no fix listed\n- sglang (PyPI): affected from 0.5.5 up to 0.5.12; no fix listed\n- sglang (PyPI): affected from 0.5.5 up to 0.5.12; 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-7302/ (Markdown: https://insights.sbomify.com/CVE-2026-7302/index.md)","id":"CVE-2026-7302","markdown":"https://insights.sbomify.com/CVE-2026-7302/index.md","name":"CVE-2026-7302","record":{"aliases":["GHSA-qwrp-wghp-94q2","PYSEC-2026-538"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SGLang multimodal runtime","requires_auth":"none","summary":"Unauthenticated attackers can write arbitrary files via path traversal in upload filenames, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"sglang","vendor":"lmsys"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-35","name":"Path Traversal: '.../...//'"}],"description":"SGLangs multimodal generation runtime is vulnerable to an unauthenticated path traversal vulnerability, allowing an attacker to write arbitrary files anywhere the server process has write access, by including ../ sequences in the upload filename when sent to specific endpoints.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CVE-2026-7302","id":"CVE-2026-7302","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Xuxueli xxl-job Execution Log JobLogController.java logDetailCat resource injection","id":"CVE-2026-7303"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.5"],"last_affected":["0.5.12"],"package":"sglang","purl":null,"source":"GHSA-qwrp-wghp-94q2"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.5"],"last_affected":["0.5.12"],"package":"sglang","purl":"pkg:pypi/sglang","source":"GHSA-qwrp-wghp-94q2"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.5"],"last_affected":["0.5.12"],"package":"sglang","purl":"pkg:pypi/sglang","source":"PYSEC-2026-538"}],"prev":{"headline":"CVE-2026-7301","id":"CVE-2026-7301"},"products":["SGLang"],"published":"2026-05-18","related":[{"cvss_score":9.8,"headline":"CVE-2026-15969","id":"CVE-2026-15969","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"CVE-2026-15971","id":"CVE-2026-15971","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"CVE-2026-15976","id":"CVE-2026-15976","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"CVE-2026-7301","id":"CVE-2026-7301","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":9.8,"headline":"CVE-2026-7304","id":"CVE-2026-7304","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":9.8,"headline":"CVE-2026-5760","id":"CVE-2026-5760","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":9.8,"headline":"CVE-2026-3059","id":"CVE-2026-3059","kev_date_added":null,"published":"2026-03-12"}],"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":"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-18","vendors":["SGLang"]},"summary":"Unauthenticated attackers can write arbitrary files via path traversal in upload filenames, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-7302/"}