{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15977 exists.","fix":"No fix has been published for CVE-2026-15977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15977 is a high-severity vulnerability in SGLang, published on 30 Jul 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-15977 and fix it if it is affected.\n\nWhat it is: CVE-2026-15977 is a high-severity vulnerability in SGLang, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15977 exists.\n\nAffected product: SGLang. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-15977/ (Markdown: https://insights.sbomify.com/CVE-2026-15977/index.md)","id":"CVE-2026-15977","markdown":"https://insights.sbomify.com/CVE-2026-15977/index.md","name":"CVE-2026-15977","record":{"aliases":["GHSA-jx7q-p32r-7wx8","GHSA-vwmc-327h-6x3j"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"SGLang inference server","requires_auth":"none","summary":"Attackers can retrieve API keys and SSL keyfile information from the /server_info endpoint when admin API key is configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"sglang","vendor":"lmsys"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"SGLang contains a credential leakage vulnerability in the /server_info endpoint, which will return API keys and SSL keyfile information when only the --admin-api-key is configured.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CVE-2026-15977","id":"CVE-2026-15977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"CVE-2026-15978","id":"CVE-2026-15978"},"packages":[],"prev":{"headline":"CVE-2026-15976","id":"CVE-2026-15976"},"products":["SGLang"],"published":"2026-07-30","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":"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-31","vendors":["SGLang"]},"summary":"Attackers can retrieve API keys and SSL keyfile information from the /server_info endpoint when admin API key is configured.","url":"https://insights.sbomify.com/CVE-2026-15977/"}