# CVE-2026-8863: CVE-2026-8863

> Attackers with admin privileges can bypass Secure Boot using vulnerable SHIM bootloaders to execute arbitrary code before OS load.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-4hqv-6cp5-4rq9

## What is CVE-2026-8863?

CVE-2026-8863 is a high-severity vulnerability in Blancco UK Abitti 1, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple Microsoft-sigend UEFI SHIM bootloaders are vulnerable to SecureBoot bypass. An attacker with administrative privileges or the ability to modify the boot process could use one of the vulnerable shim bootloaders to bypass Secure Boot protections and execute arbitrary code before the operating system loads. Specific UEFI DBX update is required to block these vulnerable boot loaders.

## Which versions are affected by CVE-2026-8863?


## How do I fix CVE-2026-8863?

No fix has been published for CVE-2026-8863 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8863 being exploited?

There is no known exploitation of CVE-2026-8863 in the wild and no public exploit code.

Public exploit code:

- Hashes and shim versions for the UEFI Secure Boot shims affected by CVE-2026-8863 (github_poc): https://github.com/0xbekoo/CVE-2026-8863

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8863 and fix it if it is affected.

What it is: CVE-2026-8863 is a high-severity vulnerability in Blancco UK Abitti 1, published on 9 Jun 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-8863 in the wild and no public exploit code.

Affected product: Blancco UK Abitti 1. 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-8863/ (Markdown: https://insights.sbomify.com/CVE-2026-8863/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8863
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8863
- OSV: https://osv.dev/vulnerability/CVE-2026-8863

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8863/
Summaries are generated and may contain mistakes; the official description above is the record.