CVE-2026-116638 The Windows Recovery Environment (WinRE) in Windows 10 and 11 may allow an attacker to bypass firmware security controls, including administ
Not scored
Published
Updated
Check this codebase for CVE-2026-116638 and fix it if it is affected.
What it is: CVE-2026-116638 is a vulnerability in n/a, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-116638 in the wild and no public exploit code.
Affected product: n/a. 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-116638/ (Markdown: https://insights.sbomify.com/CVE-2026-116638/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116638?
CVE-2026-116638 is a vulnerability in n/a, published on 26 Oct 2026.
Official description
The Windows Recovery Environment (WinRE) in Windows 10 and 11 may allow an attacker to bypass firmware security controls, including administrator-configured UEFI/BIOS passwords. An attacker with physical or administrative access to a device may be able to leverage WinRE-related boot mechanisms to circumvent firmware protections and gain unauthorized access to system resources.
Which versions are affected by CVE-2026-116638?
How do I fix CVE-2026-116638?
No fix has been published for CVE-2026-116638 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116638 being exploited?
There is no known exploitation of CVE-2026-116638 in the wild and no public exploit code.
Sources
Also known as GHSA-mr3f-4w6j-rh34.