CVE
Phison E12 secure boot bypass in SSD controller BootROM
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
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Phison E12 or E18 PCIe SSD controller
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original 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.
Who should check
Teams and vendors shipping or managing drives or devices that use Phison E12 or E18 PCIe SSD controllers
“Phison E12 and E18 PCIe SSD controllers”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Phison E12 or E18 PCIe SSD controllerWorkaround: 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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Phison E12
0
- Phison E18
0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124017
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-124017?
E12: version 0. E18: version 0.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com
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: vulncheck.com