{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-88617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88617 is a critical vulnerability in n/a, published on 15 Sep 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-88617 and fix it if it is affected.\n\nWhat it is: CVE-2026-88617 is a critical vulnerability in n/a, published on 15 Sep 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-88617 in the wild and no public exploit code.\n\nAffected product: n/a. 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-88617/ (Markdown: https://insights.sbomify.com/CVE-2026-88617/index.md)","id":"CVE-2026-88617","markdown":"https://insights.sbomify.com/CVE-2026-88617/index.md","name":"CVE-2026-88617","record":{"aliases":["GHSA-qh9f-8qc2-5365"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SmartAdmin web application","requires_auth":"none","summary":"A remote attacker can escalate privileges via an authorization flaw in the configuration query endpoint of SmartAdmin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"SmartAdmin v3.30.0 contains an authorization flaw in the configuration query endpoint. This allows a remote attacker to escalate privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2026-88617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-88618"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-88616"},"products":["n/a"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["n/a"]},"summary":"A remote attacker can escalate privileges via an authorization flaw in the configuration query endpoint of SmartAdmin.","url":"https://insights.sbomify.com/CVE-2026-88617/"}