{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-65211 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65211 is a high-severity vulnerability in SMCI MBD-X12SPI, published on 27 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-65211 and fix it if it is affected.\n\nWhat it is: CVE-2026-65211 is a high-severity vulnerability in SMCI MBD-X12SPI, published on 27 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-65211 in the wild and no public exploit code.\n\nAffected product: SMCI MBD-X12SPI. 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-65211/ (Markdown: https://insights.sbomify.com/CVE-2026-65211/index.md)","id":"CVE-2026-65211","markdown":"https://insights.sbomify.com/CVE-2026-65211/index.md","name":"CVE-2026-65211","record":{"aliases":["GHSA-v4pm-whwg-hg9x"],"analysis":null,"analysis_generated_by":null,"assigner":"Supermicro","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"This issue may allow an authenticated IPMI Administrator to read and write arbitrary BMC physical memory and thereby execute code on the BMC operating system.","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":"Supermicro BMC IPMI feature contains Critical Privilege Escalation and Arbitrary Access vulnerability","id":"CVE-2026-65211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"The reported issue was assessed as intended functionality.","id":"CVE-2026-65212"},"packages":[],"prev":{"headline":"Supermicro BMC IPMI feature contains Arbitrary File Access vulnerability","id":"CVE-2026-65210"},"products":["MBD-X12SPI"],"published":"2026-10-27","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-27","vendors":["SMCI"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-65211/"}