SECUFOCUSNOW
Home›CVE index›CVE-2026-8863
Review reviewHigh

CVE-2026-8863

Oracle Corporation OracleLinux(7.2) shim, Service Center Enterprise, Service Center Drive Erase

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.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.06.10
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Oracle Corporation OracleLinux(7.2) shim, Service Center Enterprise, Service Center Drive Erase
Affected versions
>= 0.9, >= 14 <= 17.0.7536.900, >= 15 <= 17.0.7538.592, >= 15 <= 17.0.7539.904, >= 14 <= 17.0.7535.900, >= 6.9 <= 6.20.7711.267, >= 6.9 <= 6.20.7710.267, >= 4.2, >= 8.0.0 <= 8.1.3, <= 2024R1, >= 1.0.0, >= R9, >= R10
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Oracle Corporation OracleLinux(7.2) shim, Service Center Enterprise, Service Center Drive Erase and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available