Security readout for executives and security teams
Plain-English summary
Affected Phison PS3111-S11 storage-controller firmware can accept privileged commands without reliable authentication. An attacker who already has high local privileges could manipulate controller memory or raw flash, potentially creating storage-level implants that survive power cycles and compromise confidentiality, integrity, and availability.
Executive priority
Treat as an urgent targeted-risk issue, not an internet-wide emergency. Rapidly identify affected controllers in sensitive systems, especially administrator workstations, security infrastructure, and devices requiring strong persistence resistance. Escalate replacement decisions if no vendor-supported firmware remedy is available.
Technical view
Firmware versions reported through SBFQT1.3 expose privileged vendor-unique commands over ATA. Authentication may be absent or bypassable because the unlock mechanism relies on weak CRC-16. Successful access permits controller-memory and raw-flash reads and writes. The supplied CVSS 4.0 score is 9.3, with local access and high privileges required.
Likely exposure
Exposure is limited to systems containing the Phison PS3111-S11 controller with affected firmware through SBFQT1.3. Exploitation requires local access and high privileges, reducing initial reach but making compromised administrator accounts, malicious insiders, and already-breached endpoints relevant scenarios. The bundle does not identify specific drive models.
Exploitation context
Public exploit-oriented research repositories are referenced, demonstrating technical accessibility. However, this CVE is not listed in KEV, and the supplied sources do not establish active exploitation in the wild. The requirement for high local privileges makes this primarily a post-compromise persistence and impact risk.
Researcher notes
CWE-306 applies because privileged vendor-unique commands lack effective authentication. The principal security boundary failure is below the operating-system storage layer, enabling persistent controller or flash modification after privileged local access. Evidence supports exploit feasibility, but the bundle provides no confirmed campaign activity, named fixed version, or comprehensive affected-device mapping.
Mitigation direction
- Inventory storage devices for the PS3111-S11 controller and record firmware versions.
- Check Phison and device-vendor guidance for fixed firmware or supported replacement options.
- Restrict administrative access and raw ATA pass-through capabilities to trusted personnel and software.
- Prioritize replacement or isolation where verified remediation is unavailable and system sensitivity is high.
Validation and detection
- Confirm controller identity and firmware version using approved asset or vendor tooling.
- Compare identified firmware against the reported affected range through SBFQT1.3.
- Review endpoint controls and logs for unauthorized privileged storage-management activity.
- After remediation, verify the installed firmware or replacement hardware against vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-84696 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H1.56VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://trulycrisp.github.io/drivefirmware/phison_s11/CVE reference, VulnCheck · technical-description
- https://github.com/trulycrisp/psychiteCVE reference, VulnCheck · exploit
- https://github.com/trulycrisp/disksecCVE reference, VulnCheck · exploit
- VulnCheck Advisory: Phison PS3111-S11 Controller Firmware Missing Authentication on Vendor Unique CommandsCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Functionality
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.