CVE-2026-6485 UEFI BIOS embedded Shell can be used to bypass Secure Boot
High 8.2
Published
Updated
Check this codebase for CVE-2026-6485 and fix it if it is affected.
What it is: CVE-2026-6485 is a high-severity vulnerability in InsydeH2O, published on 9 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6485 in the wild and no public exploit code.
Affected product: InsydeH2O. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-6485/ (Markdown: https://insights.sbomify.com/CVE-2026-6485/index.md)
Attackers can bypass Secure Boot protections using the embedded UEFI Shell, compromising system integrity on devices running InsydeH2O firmware.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6485?
CVE-2026-6485 is a high-severity vulnerability in InsydeH2O, published on 9 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
UEFI BIOS embedded Shell could be used to bypass Secure Boot via shell commands or startup scripts.
Weakness: CWE-489
Which versions are affected by CVE-2026-6485?
How do I fix CVE-2026-6485?
No fix has been published for CVE-2026-6485 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-6485 being exploited?
There is no known exploitation of CVE-2026-6485 in the wild and no public exploit code.
Sources
Also known as AZL-100017, AZL-99990, GHSA-j5ph-5jrp-hf3x.